It would go something like this:
<invoke partnerLink="myUDDIservice" operation="getServiceEndpoint"
inputVariable="serviceNameOrOther"
outputVariable="selectedEndpoint" />
<assign>
<copy>
<from variable="selectedEndpoint"/>
<to partnerLink="dynamicEndpointPartner"/>
</copy>
</assign>
<invoke partnerLink="dynamicEndpointPartner" operation="doSomething" ... />
alex
On 3/14/07, Azon <[EMAIL PROTECTED]> wrote:
Thank you for your answer.
What do you mean by using assignments or service invocation ?
Azon.
Alex Boisvert wrote:
>
> On 3/14/07, Azon <[EMAIL PROTECTED]> wrote:
>>
>>
>> My process has to call external web services. I would like to know how
>> the
>> external services locations are managed ?
>> Does Ode invokes an endpoint by looking up the service name in the WSDL
>> to
>> find the endpoint (e.g., the <soap:address>) ? Is it possible to lookup
>> an
>> UDDI in order to retrieve the Web Services endpoints.
>
>
>
> Yes, Ode retrieves the endpoint from WSDL descriptions (service + port
> name). You may also dynamically compute the endpoint, using
assignments
> or
> service invocation. This approach would allow you to retrieve
> information
> from a UDDI registry provided you have a service implementation to do
such
> lookup as Ode doesn't natively support UDDI.
>
> cheers,
> alex
>
>
--
View this message in context:
http://www.nabble.com/Invoked-services-endpoints-tf3401513.html#a9473550
Sent from the Apache Ode User mailing list archive at Nabble.com.
