Hello,
I've been exploring various UDDI solutions and I think jUDDIv3 is a good solution, but I have some concerns. 1) I've seen it stated that "jUDDIv3 only supports the UDDI v3 protocol". I've seen this in action as I cannot use the Eclipse Web Services Explorer or the Oracle Service Bus 11g to connect to jUDDIv3. It would seem that there are tons of UDDIv2-based products already out there and that jUDDIv3 not supporting them is a big limitation. The problem seems simple (on the surface) to solve...allowing the old v2-namespace-service calls to still occur in the jUDDIv3...basically exposing the old v2 services, but call the newer implementation code? Is there a reason this was not allowed (in the spec)? 2) There is a nice .class under development in the uddi-client code called "WSDL2UDDI.java", but it only implements 2 of the 5 parts required to represent a Web Service in the UDDI data structure. Is anybody working on this currently? (I know that since this is open-source I should finish it myself ;) and submit it, but before I spend time on it, I'd like to know if its already in the works...especially since it was last touched in about January?) 3) The portal console is nice, but it does not replace the functionality that was in the v2 console which let you invoke every method. The only way to publish a service now is programatically. Is there anything in the works on this one? Thanks! Jeffrey L. McCain
