MSServices

UPDATED RELEASE: MS.Services 1.1.0 (Jan 26, 2008)

Fri, 11 Apr 2008 06:06:09 GMT

Added support for SQLite, MySql, PostgreSQL.
Added SQL Executor to execute direct SQL statements (Also validator and shield).
Added support for Adobe Flex 3 Data access.
Now output parameters can be set to Cookies.
"MapFieldsToRecords" property is added to JSON generator.
If this value is true, the "RecordSet" Property of JSON output is array of hashtable(Javascript Object) instead of two dimensional array.

If you have any other questions or suggestions feel free to contact me from mertsakarya@hotmail.com

Source code checked in

mertsakarya — Sat, 08 Mar 2008 17:15:54 GMT

Source code checked in

mertsakarya — Sat, 08 Mar 2008 17:15:22 GMT

Source code checked in

mertsakarya — Sat, 08 Mar 2008 17:14:17 GMT

UPDATED RELEASE: MS.Services 1.1.0 (Jan 26, 2008)

Sat, 02 Feb 2008 11:11:50 GMT

UPDATED RELEASE: MS.Services 1.1.0 (Jan 26, 2008)

Fri, 01 Feb 2008 16:21:25 GMT

UPDATED WIKI: Home

mertsakarya — Mon, 28 Jan 2008 05:56:31 GMT

Project Description
This project is an SOA application server for HTTP. It can execute Database SPs, MSMQ, Assemblies, IronPython script and generates JSON, Web Service, Text, Excel or RSS file through HTTP. The system has authentication, caching, compression and logging support.

Everything came to my mind, when I saw the "SQLXML and IIS support", which lets you execute Stored Procedures and generate XML as response on the Web. But it had some restrictions for the database, authentication/authorization and format of the generated output.

This project lets you create URLs like below very easily (without writing a single line of code) which can be used on AJAX Web applications or as Web Services;

http://www.domain.com/<VPath>/<ServiceName>.<AtomName>.<Ext>?<Param1>=<Value1>&...&<ParamN>=<ValueN>
eg. http://localhost/Web/Northwind.GetCustomerOrders.ws?CustomerID=ALFKI

Where;

<VPath> is the Virtual Path of the application,
<ServiceName> is the name of the web service,
<AtomName> is the name of the method to execute,
<Ext> is the name of the file extension, which can be (ws -for web service, txt -for text file, json -for Javascript output, xls -for excel files)
<Param1>=<Value1>&<Param2>=<Value2> are the names and values of the parameters to pass to the Atom

The request above executes on the server-side and generates an output of the specified extension. Before executing the "Atom", it checks the credentials, authorization, validates the parameters and validates the relationship between parameters. It also Logs, Caches and Compresses the results.

If you are using Enterprise Library, it is very easy to configure the application.

Everything starts with "MS Services Application Block" and under that block you can define "Services" and "Shields". Shields are used to protect Services. A Service is very similiar to a Web Service with some exceptions. Services have executables named "Atoms" and "Categories" to categorize Atoms. Atoms have an "Executor" and "Generators". Atoms also have "Parameters", "Shields" and "Caching Options". Parameters have "Validators" to be validated before executing. There are two special Atoms named "User" which is used for authentication and "Exception" that reports exceptions occured during executing.

There are many "Wizards" that help you to generate Services and Atoms.

With these concepts mentioned above, you can easily create "Web Services" that connects to server-side data and returns the result. For example, when you select the "Wizard: Create Atoms from SQL Server Database" wizard under "New" command by right-clicking a Service node in "Enterprise Library Configuration Tool", you select the database connection and select Stored Procedures, then they are available as Atoms with parameters that generates Excel documents, Web Services or Text Files.

Recently added

"File Executor".
This executor, reads a local file, caches it in memory (if necessary) and writes output depending on extension, but it also have a "WriteRaw" property that lets program to ignore extension. This executor can be used if you want authentication, logging, etc. You can also select file names depending on parameters passed.

"SQL Executor"
To execute SQL statements directly from databases.

More database support
MS.Services now supports SQLite, MySql and PostgreSQL. Actually, adding this feature was very easy, thanks to the design of Enterprise Library.

Support for Adobe Flex and AIR
With asdl extension, MS.Services generates ActionScript file for use with Flex. This support is on beta now.

Currently I keep improving the project. It definitely needs a good installer and a documentation. So if you need any help or questions about the project, please don't hesitate to contact me at mertsakarya@hotmail.com

UPDATED RELEASE: 1.0.3 Production

Sat, 26 Jan 2008 07:15:26 GMT

This release is going to have "XML Executors" and "Ignored parameters".

RELEASED: MS.Services 1.1.0 (Jan 26, 2008)

Fri, 25 Jan 2008 22:27:54 GMT

UPDATED RELEASE: MS.Services 1.1.0 (Jan 26, 2008)

Fri, 25 Jan 2008 22:27:54 GMT

UPDATED RELEASE: MS.Services 1.1.0 (Jan 26, 2008)

Fri, 25 Jan 2008 22:24:23 GMT

Added support for SQLite, MySql, PostgreSQL.
Added SQL exector to execute direct SQL statements.
Now output parameters can be set to Cookies.
Added support for Adobe Flex 3 Data access.

CREATED RELEASE: MS.Services 1.1.0 (Jan 26, 2008)

Fri, 25 Jan 2008 22:22:23 GMT

Added support for SQLite, MySql, PostgreSQL.
Added SQL exector to execute direct SQL statements.
Now output parameters can be set to Cookies.
Added support for Flex Data access.

UPDATED WIKI: Home

mertsakarya — Fri, 25 Jan 2008 21:44:55 GMT

http://www.domain.com/<VPath>/<ServiceName>.<AtomName>.<Ext>?<Param1>=<Value1>&...&<ParamN>=<ValueN>
eg. http://localhost/Web/Northwind.GetCustomerOrders.ws?CustomerID=ALFKI

Where;

<VPath> is the Virtual Path of the application,
<ServiceName> is the name of the web service,
<AtomName> is the name of the method to execute,
<Ext> is the name of the file extension, which can be (ws -for web service, txt -for text file, json -for Javascript output, xls -for excel files)
<Param1>=<Value1>&<Param2>=<Value2> are the names and values of the parameters to pass to the Atom

The request above executes on the server-side and generates an output of the specified extension. Before executing the "Atom", it checks the credentials, authorization, validates the parameters and validates the relationship between parameters. It also Logs, Caches and Compresses the results.

If you are using Enterprise Library, it is very easy to configure the application.

Everything starts with "MS Services Application Block" and under that block you can define "Services" and "Shields". Shields are used to protect Services. A Service is very similiar to a Web Service with some exceptions. Services have executables named "Atoms" and "Categories" to categorize Atoms. Atoms have an "Executor" and "Generators". Atoms also have "Parameters", "Shields" and "Caching Options". Parameters have "Validators" to be validated before executing. There are two special Atoms named "User" which is used for authentication and "Exception" that reports exceptions occured during executing.

There are many "Wizards" that help you to generate Services and Atoms.

With these concepts mentioned above, you can easily create "Web Services" that connects to server-side data and returns the result. For example, when you select the "Wizard: Create Atoms from SQL Server Database" wizard under "New" command by right-clicking a Service node in "Enterprise Library Configuration Tool", you select the database connection and select Stored Procedures, then they are available as Atoms with parameters that generates Excel documents, Web Services or Text Files.

Recently added
"File Executor".
This executor, reads a local file, caches it in memory (if necessary) and writes output depending on extension, but it also have a "WriteRaw" property that lets program to ignore extension. This executor can be used if you want authentication, logging, etc. You can also select file names depending on parameters passed.

"SQL Executor"
To execute SQL statements directly from databases.

More database support
MS.Services now supports SQLite, MySql and PostgreSQL.

Support for Flex 3
With asdl extension, MS.Services generates ActionScript file for use with Flex. This support is beta now.

Currently I keep improving the project. It definitely needs a good installer and a documentation. So if you need any help or questions about the project, please don't hesitate to contact me at mertsakarya@hotmail.com

Source code checked in

mertsakarya — Fri, 28 Sep 2007 08:36:52 GMT

Source code checked in

mertsakarya — Fri, 28 Sep 2007 08:35:58 GMT

Patch Uploaded

gsneden — Sat, 23 Jun 2007 00:51:54 GMT

gsneden has uploaded a patch.

Description:
this is only a test, we are testing site usability. thanks

CLOSED ISSUE: Add XML Executor

mertsakarya — Mon, 18 Jun 2007 20:09:19 GMT

Add an XML executor, that loads an XML document in memory, and executes an XPath expression against it then returns the matched row(s).

COMMENTED ISSUE: Add XML Executor

mertsakarya — Thu, 07 Jun 2007 08:04:06 GMT

Add an XML executor, that loads an XML document in memory, and executes an XPath expression against it then returns the matched row(s). Comments: ** Comment from web user: mertsakarya **

Done in the next release it will be published.

UPDATED WIKI: Home

mertsakarya — Sun, 27 May 2007 18:44:03 GMT

Project Description
This project is another way to create SOA applications through HTTP. It can execute Database SPs, MSMQ, Assemblies, IronPython script and generates JSON, Web Service, Text, Excel or RSS file through HTTP. The system has authentication, caching, compression and logging support.

Everything came to my mind, when I saw the "SQLXML and IIS support", which lets you execute Stored Procedures and generate XML as response on the Web. But it had some restrictions for the database, authentication/authorization and format of the generated output.

This project lets you create URLs like below very easily (without writing a single line of code) which can be used on AJAX Web applications or as Web Services;

http://www.domain.com/<VPath>/<ServiceName>.<AtomName>.<Ext>?<Param1>=<Value1>&...&<ParamN>=<ValueN>
eg. http://localhost/Web/Northwind.GetCustomerOrders.ws?CustomerID=ALFKI

Where;

<VPath> is the Virtual Path of the application,
<ServiceName> is the name of the web service,
<AtomName> is the name of the method to execute,
<Ext> is the name of the file extension, which can be (ws -for web service, txt -for text file, json -for Javascript output, xls -for excel files)
<Param1>=<Value1>&<Param2>=<Value2> are the names and values of the parameters to pass to the Atom

The request above executes on the server-side and generates an output of the specified extension. Before executing the "Atom", it checks the credentials, authorization, validates the parameters and validates the relationship between parameters. It also Logs, Caches and Compresses the results.

If you are using Enterprise Library, it is very easy to configure the application.

Everything starts with "MS Services Application Block" and under that block you can define "Services" and "Shields". Shields are used to protect Services. A Service is very similiar to a Web Service with some exceptions. Services have executables named "Atoms" and "Categories" to categorize Atoms. Atoms have an "Executor" and "Generators". Atoms also have "Parameters", "Shields" and "Caching Options". Parameters have "Validators" to be validated before executing. There are two special Atoms named "User" which is used for authentication and "Exception" that reports exceptions occured during executing.

There are many "Wizards" that help you to generate Services and Atoms.

With these concepts mentioned above, you can easily create "Web Services" that connects to server-side data and returns the result. For example, when you select the "Wizard: Create Atoms from SQL Server Database" wizard under "New" command by right-clicking a Service node in "Enterprise Library Configuration Tool", you select the database connection and select Stored Procedures, then they are available as Atoms with parameters that generates Excel documents, Web Services or Text Files.

Recently I added "File Executor".
This executor, reads a local file, caches it in memory (if necessary) and writes output depending on extension, but it also have a "WriteRaw" property that lets program to ignore extension. This executor can be used if you want authentication, logging, etc. You can also select file names depending on parameters passed.

Currently I keep improving the project. It definitely needs a good installer and a documentation. So if you need any help or questions about the project, please don't hesitate to contact me at mertsakarya@hotmail.com

CREATED FEATURE: Parameters should be ignored when passing to executors.

mertsakarya — Wed, 25 Apr 2007 21:40:33 GMT

Add a features to ignore parameter when passing to executors. This could be done by, *"MapTo"* feature that has a *"Ignore"* value. This feature lets parameters to be defined and used for shields and validators, but not passed to executors.