Davanum Srinivas wrote:
Deepak,
+1 to #1 patch. Not so sure about #2. Can you please explain a bit
more why ebxmlrr support is desired/necessary?
#2 is necessary so we have a level 1 JAXR client, i.e., so that we can
access both UDDI and ebXML registries.
The ebxmlrr code that was imported is an open source JAXR provider for
ebXML -- we have the UDDI provider already, of course. (the "providers"
are chosen by using the specific Factory in JAXR).
According to a Sun's J2EE Evangelist (Prof. Sang Shin), people are using
both, including the most common case of using a UDDI registry to find
the ebXML registry. This was two years ago, of course, and before UDDI 3.
Cheers,
Fernando
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
