|
Overview |
  
|
|
Overview |
|
WebORB fully supports the JSON format for remote method invocations. Any deployed service, including .NET classes from class libraries, WCF services, Spring.NET objects, NHibernate models and Web Services, can be invoked from a JSON client. All server-side features, including service security, service activation, service and argument factories, invocation monitoring, and abstract arguments, are applicable to the JSON invocations.
In the current implementation incoming requests must be delivered over HTTP/HTTPS and sent to a URL mapped to the WebORB http hander (weborb.aspx). Requests must have the Content-Type header set to "application/json". The ID of the service targeted in the invocation must be specified in the query string of the request with the name of the key set to "target". For example, the following HTTP request invokes a method in the Weborb.Examples.BasicService class:
http://localhost/weborb4/weborb.aspx?target=Weborb.Examples.BasicService
WebORB/JSON integration follows the JSON-RPC structure of the requests. Method name must be set using the "method" property of the request. Method arguments must be specified using the "params" key.
Integration supports invocations of method accepting and returning data types which can be primitive values, complex types and arrays of primitive values, complex types.