Good to hear that you got things working.
- As far as JBoss-AS7 goes, JAXR (Scout) and the juddi-client libs ship
by default. So you can use it out of the box, for more info see
http://apachejuddi.blogspot.com/2012/02/using-jaxr-on-jboss-711.html
- I have not yet tried to deploy the jUDDI server. jUDDI is a simple war
with JAX-WS based webservices so I don't expect to you'd encounter any
issues, but you may need to work your way to some lib version and config
issues. You would not need to ship the WS and JPA stack in the jUDDI war
since the appserver already has them, so you should be able to use a
very light jUDDI war. I would think it wouldn't be all that different
from using AS-6. I do know there are plans to ship JUDDI v3 as a module
on AS-7 for the JBoss SOA Platform, but that's a bit different then
using the war. Please let us know how what you find out and maybe we can
help.
Cheers,
--Kurt
On 6/7/12 9:24 AM, tech evaluator wrote:
Thanks Kurt for your response.
I have been able to publish and search external wsdls using publish
and Inquiry APIs.
My next usecase is as follows:
The juddi user guide describes how to deploy juddi to JBoss 6.0.0.GA
<http://6.0.0.GA>.
But I need to use juddi with JBoss application server 7.1.
Could you please let me know if it is feasible and any guidelines for
the same.
-Thanks
On Thu, May 31, 2012 at 7:58 PM, Kurt T Stam <[email protected]
<mailto:[email protected]>> wrote:
Hi 'tech_evaluator',
jUDDI is registry that implements the UDDI v3 specification. You
can register the WSDL using the appropriate UDDI Publish APIs.
If you want more help on the client side and you want to use the
model suggested by these technotes:
http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm
then we have a WSDL2UDDI class in out client that you can use.
https://svn.apache.org/repos/asf/juddi/trunk/juddi-client/src/main/java/org/apache/juddi/v3/client/mapping/WSDL2UDDI.java
It is nearly implements the entire technote, and you can embed
that in your client. If you decide to complete that mapping we'd
greatly appreciate a patch (see also
https://issues.apache.org/jira/browse/JUDDI-5140).
Cheers,
--Kurt
On 5/31/12 7:22 AM, tech_evaluator wrote:
I need to register a SOAP based web service which is deployed
on one remote
server (say tomcat) and i don't have access to the java code
of that web
service and I just have the wsdl url of that web service.
Now I need to register this service( WSDL URL) in juddi
service registry.
Ques:-->
1-Does jUDDI service registry provide this capability to
register an
external wsdl url. (e.g Mule Galaxy service registry does
provide this
functionality to register wsdl url.)
2-If yes, what is the approach for the same for juddi service
registry.
