There's only one way to store anything in UDDI and that's through UDDI's publishing API. So I am guessing the matchmaker uses this API to store the OWL profiles in the embedded jUDDI. To get it to work with jUDDI v3 you would need to isolate the code that calls the publishing API, and make it compatible with jUDDI v3. That will involve interacting with v3 using the new client API and using the new XML data classes.
-----Original Message----- From: n3mesi83 [mailto:[email protected]] Sent: Monday, October 11, 2010 11:02 AM To: [email protected] Subject: juddi and owls Hi all, I installed juddiv3, the portal bundle on ubuntu server and now i would like to search for services using their owls descriptions...i found owls/uddi matchmaker, which takes advantage of UDDI’s proliferation in the web service technology infrastructure and OWL-S’s explicit capability representation. In order to achieve this symbiosis i need to store the OWL-S profile descriptions inside an UDDI registry. The matchmaker i've downloaded is implemented as an extension of the JUDDI. The problem: the matchmaker installation guide says that i don't need to install jUDDI since it is included in the default installation package...but the version of juddi is 0.8...i would like to use juddiv3... the question is: how can i add the matchmaker in juddiv3? Or maybe there is another technology that allows me to publish the owls? I would like to search a web service using its semantic information with JENA framework and its OWL API. Thanks. -- View this message in context: http://old.nabble.com/juddi-and-owls-tp29935373p29935373.html Sent from the jUDDI - User mailing list archive at Nabble.com.
