[
https://issues.apache.org/jira/browse/OFBIZ-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874617#action_12874617
]
Adrian Crum commented on OFBIZ-3798:
------------------------------------
I don't understand your comment - sorry.
Calling xml-rpc is no different than calling an OFBiz service, except the
service is run on a remote server. So, why not set up a call-xml-rpc simple
method that works just like call-service? The location attribute would contain
the remote server's URL, The service-name attribute would contain the xml-rpc
methodName, the in-map-name attribute specifies a Map of parameters to send to
the remote service, etc. When the remote service call returns, the returned
values are mapped to a result Map - just like an OFBiz service.
<call-xml-rpc location="http://someXmlRpcServer.com/path/to/xmlrpc";
service-name="someService" in-map-name="xmlRpcServiceMap"/>
Doing it this way, there is no need for a generic service.
> Add generic service to call xml-rpc request
> -------------------------------------------
>
> Key: OFBIZ-3798
> URL: https://issues.apache.org/jira/browse/OFBIZ-3798
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Nicolas Malin
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: xml-rpc.diff
>
>
> I add a generic service to call xml-rpc server. The goal is to have a
> technical interface to make calls directly from mini-lang.
> The first patch it's my draft. I don't know where I do the service
> definition. I add a servicedef in framework/webapp, I move service on
> framework/common ? any suggest are welcom ;)
> Nicolas
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
