[CONF] Apache Ode: Endpoint Configuration (page edited)

Tue, 15 Jul 2008 15:06:35 -0700

Page Edited : ODExSITE : Endpoint Configuration

Endpoint Configuration has been edited by Alexis Midon (Jul 15, 2008).

(View changes)

Content:

SOAP-bound EPR configuration

If you deploy ODE in an application server, the Axis2 Integration Layer allows ODE to communicate via Web Service interactions. SOAP-bound Web Services will be managed by Axis2. These web services may be configured dynamically.
For each service, you need to place a [serviceLocalName].axis2 file at the root of the process bundle. Currently, this file can only be added on the server, under var/processes/[PROCESS].

For example, given this wsdl: 

<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions ...>
  <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">A sample Time service</wsdl:documentation>
 ...
  <wsdl:service name="TimeService">
    <wsdl:port name="TimeServiceSoap" binding="tns:TimeServiceSoap">
      <soap:address location="http://ws.intalio.com/TimeService/" />
    </wsdl:port>
  </wsdl:service>
</wsdl:definitions>


You would place a TimeService.axis2 file with: 




<service name="TimeService" scope="application" targetNamespace="http://ws.intalio.com/TimeService/">
    <module ref="sandesha2" />
    <module ref="addressing" />
</service>




This will engage Engage sandesha2 and addressing modules.



For further details about the type of parameters that can be set, see Axis2 Service Config.



On every request, if the config file has not been polled during the last 30 seconds then check the file for updates. If any, (re)load it.

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences

Reply via email to