2 Replies Latest reply on Mar 25, 2011 1:46 PM by everjava

Differents configuration for jUDDI Transports, between documentation and file configured

everjava Mar 24, 2011 1:27 PM

I'm trying to install jbossesb + juddi and the documentation there's a code in 1.2.4 Using jUDDI Transports:

But, in the file esb.juddi.client.xml from jbossesb.sar(jboss5.1, jbossesb4.9) there's

<proxyTransport>org.jboss.internal.soa.esb.registry.client.JuddiRMITransport</proxyTransport>

I'd like know what's the best choice ?

1. Differents configuration for jUDDI Transports, between documentation and file configured

tcunning Mar 24, 2011 7:25 PM (in response to everjava)

Use JuddiRMITransport.java. There was an issue with jUDDI's implementation of an RMI transport where it was ignoring the JNDI settings on a remote machine (https://issues.jboss.org/browse/JBESB-3071), which is why ESB contains its own version of an RMI transport for jUDDI.

I'm not sure whether that issue has been resolved or not, but I'll look into it and log a bug to fix the documentation issue you've raised here.
Actions
2. Re: Differents configuration for jUDDI Transports, between documentation and file configured

everjava Mar 25, 2011 1:46 PM (in response to tcunning)

Thanks !!

Other thing is that I've saw some /juddiv3 in configuration files*, but in juddi-service.sar there's juddi.war, in this case /juddi

eg:
esb.juddi.client.xml
<inquiryUrl>/juddiv3/UDDIInquiryService</inquiryUrl>

*****************

in jboss-properties.xml there's:
<property name="org.jboss.soa.esb.registry.queryManagerURI" value="org.apache.juddi.v3.client.transport.wrapper.UDDIInquiryService#inquire"/>

and in documentation:
http://docs.jboss.org/jbossesb/docs/4.9/manuals/html/Services_Guide/index.html#d0e113

<property name="org.jboss.soa.esb.registry.queryManagerURI" value="org.apache.juddi.registry.local.InquiryService#inquire" />

Is this right ?
Actions