[ 
https://issues.apache.org/jira/browse/OFBIZ-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877070#action_12877070
 ] 

Nicolas Malin commented on OFBIZ-3798:
--------------------------------------

I rename Jira for better understanding.

To resolv my problem to store information need by engine as xml-rpc I propose 
two solution.

1. I add config on service-engine to have a solution has :
   <engine name="xml-rpc-server1" class="org.ofbiz.service.engine.XmlRpcEngine">
        <parameter field="server.login" value="XXX"/>
        <parameter field="server.password" value="YYY"/>
   </engine>
   <engine name="xml-rpc-server2" class="org.ofbiz.service.engine.XmlRpcEngine">
        <parameter field="server.login" value="ZZZ"/>
        <parameter field="server.password" value="EEE"/>
        <parameter field="server.keys" value="AZERTY"/>
        <parameter field="server.auth" value="http://tiers.com"/>
   </engine>

and service definition :
<service name="XmlRpcCallServiceExample" engine="xml-rpc-server1" 
location="http://XmlRpcServer/path/to/connector"; invoke="MethodName">
...
</service>

<service name="XmlRpcCallServiceExample2" engine="xml-rpc-server2" 
location="http://XmlRpcServer/path/to/connector"; invoke="MethodName">
...
</service>

OR 

2. I add an attribute to service definition to given a properties ressources as 
:

<service name="XmlRpcCallServiceExample" engine="xml-rpc" 
location="http://XmlRpcServer/path/to/connector"; invoke="MethodName" 
engine-config="XmlRpcServer1.properties">
...
</service>

<service name="XmlRpcCallServiceExample2" engine="xml-rpc" 
location="http://XmlRpcServer/path/to/connector"; invoke="MethodName"> 
engine-config="XmlRpcServer2.properties" >
...
</service>

Config file present in hot-deploy (hors other)
XmlRpcServer1.properties :
    login=XXX
    password=YYY
XmlRpcServer2.properties :
    login=ZZZ
    password=AAA
    keys=AZERTY
    auth=http://tiers.com

The first solution give the possibility to define engine oriented on process 
but need change the serviceengine.xml 
The second solution is less generic than the first but more easier to custom 
customer server.

At your comments ;)

> Add xml-rpc engine on serviceengine
> -----------------------------------
>
>                 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, XmlRpcEngine.patch
>
>
> 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.

Reply via email to