Paul
This would be good.. also we could support other Registries than UDDI,
and this could be similar in implementation to the WSDL endpoint
asankha
Paul Fremantle wrote:
Ruwan
I believe what Eddie is proposing is to pull the endpoint definition
from UDDI instead of from WSDL.
So instead of
<endpoint>
<wsdl...../>
</endpoint>
You would have
<endpoint>
<uddi ....>
</endpoint>
This would look up the endpoint URL from UDDI. In fact there probably
would be two options - one is simply to look up the URL in UDDI (using
a UDDI endpoint definition) and the second is to pull a full WSDL from
UDDI (http://www.ibm.com/developerworks/webservices/library/ws-wsdl/)
Its been a while since I really studied UDDI, but I guess the main
thing we should do is to define what the <uddi/> tag needs as input,
and then once we have that clearly defined, we can code it and test
against some implementations.
Paul
On Sun, Jun 29, 2008 at 1:19 PM, Ruwan Linton <[EMAIL PROTECTED]> wrote:
Hi Eddie,
Hi there,
i want to integrate jUDDI and Synapse too.
can i join?
any proposed scope?
For the moment there is no built-in integration with jUDDi, if you need this
feature, you may go ahead and file a JIRA for this.
http://issues.apache.org/
to me, it will be very useful if it can easily connect to jUDDI as one of
the endpoint types
What do you mean by endpoint type here, AFAIK jUDDI is a registry right?
Thanks,
Ruwan
Eddie Lau
--
View this message in context:
http://www.nabble.com/-Synapse-1.1.1--problems-with-XML-request-tp17336164p18176973.html
Sent from the Synapse - User mailing list archive at Nabble.com.
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
