Community
Participate
Working Groups
XML-RPC is more simple then SOAP protocol for remote method invocation via HTML. We can use org.apache.xmlrpc from ORBIT for this task.
This is a good idea. It should be fairly straightforward, given the xml-rpc bundle in Orbit as Pavel mentions.
Changing target milestone.
Currently status. XML-RPC Provider classes Bundle: org.eclipse.ecf.remoteservice.rpc Location: http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/tree/framework/bundles/org.eclipse.ecf.remoteservice.rpc Status: Under active development XML-RPC Provider feature Feature: org.eclipse.ecf.remoteservice.rpc.feature Location: http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/tree/releng/features/org.eclipse.ecf.remoteservice.rpc.feature Status: Under preparing for releng works Tests Bundle: org.eclipse.ecf.tests.remoteservice.rpc Location: http://git.eclipse.org/c/ecf/org.eclipse.ecf.git/tree/tests/bundles/org.eclipse.ecf.tests.remoteservice.rpc Status: Today (01/25/11) all tests passed Currently the provider supports followed things: - RemoteServicesClient API (Sync and Async invokes via Callable/Call); - Remote Service invokation via Proxy (if a server is based on the Apache XML-RPC library); - Custom input parameters serializers (i.e. java objects into RPC-friendly types serializers). Currently the provider does not support: - HTTP headers relation authentification; - custom datatypes, but I'm planning to finish this work on early Feb 2011.
XML-RPC addon is available from the http://build.ecf-project.org/repo/C-HEAD-remoteservice.rpc.feature/lastSuccessful/archive/site.p2/ updatesite.
Given comment 4, I'm resolving this as fixed. Congratulations and Thanks to Pavel...this a great contribution.
Pavel, I thought I would try to use the xml-rpc remote services provider for OSGi remote services (and the new remote service admin) with the 'hello' examples, but when I went to define an XML-RPC server (for the remote service host), I didn't find an xml-rpc server in the xml-rpc provider. i.e. there was the 'ecf.xmlrpc.client' but no 'ecf.xmlrpc.server' that I could find. Is there (or could there) be an xml-rpc remote services server? Is this just something that you haven't gotten to? BTW, I've also been contemplating adding a rest remote service host API...i.e. something that could be used with restlet API. Maybe this is also needed here (?)
Hello Scott, I made only client API for XML-RPC. I think we need some common API for web-services, REST, XML-RPC server part and we should realize the adapters using this commons API. Also for server side. XML-RPC is supported only some datatypes (int, string, double, etc) and we need some datatype mapping convention that define how Java-classes will be mappings to XML-RPC supported types.
(In reply to comment #7) > Hello Scott, > > I made only client API for XML-RPC. I think we need some common API for > web-services, REST, XML-RPC server part and we should realize the adapters > using this commons API. Yes, I agree. I've been thinking for some time about an API for server-side REST-based OSGi services...but not been able to do much around that yet. My expectation is that the IRemoteServiceContainerAdapter.registerRemoteService would have some REST-API-specified service object that to expose rest-based remote services. > > Also for server side. XML-RPC is supported only some datatypes (int, string, > double, etc) and we need some datatype mapping convention that define how > Java-classes will be mappings to XML-RPC supported types. Can't XML RPC use java object serialization somehow? In any case, I agree with you that this is another server-side design question.
