> 4) Paul Fremantle said:
>
>> I suggest you start by implementing a UDDI endpoint, that gets the
>> actual endpoint from UDDI. I can help out.[...]
When a service (WSDL) is loaded into UDDI, the UDDI server "splits"
the file and extracts the endpoint address (URL) and makes it
available to be found using a key ("tModel"). So what I'm suggesting
is that we write a new type of endpoint:
<endpoint>
<uddi tmodel=".....">
<parameter
name="uddi.server.url">http://youruddiserver:8080/</parameter>
<parameter name="uddi.auth.uid">userid</parameter>
<parameter name="uddi.auth.pw">password</parameter>
</uddi>
</endpoint>
Its been a while since I looked at UDDI, so you could start by reading
the spec and understanding how WSDLs are published into UDDI and how
services are found. From there it should be easy to code an endpoint
implementation.
Paul
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
