-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 5.1.0.ER2
-
Fix Version/s: 5.1.0 GA
-
Component/s: jUDDI - within SOA
-
Labels:
-
Release Notes Text:
-
Release Notes Docs Status:Documented as Resolved Issue
Retrieving any service with the jUDDI client via JAXWSTransport ends with this exception:
org.apache.juddi.v3.client.transport.TransportException:
{urn:uddi-org:v3_service}UDDI_Security_Port is not a valid service. Valid services are:
{urn:uddi-org:v3_service}UDDISecurityService
at org.apache.juddi.v3.client.transport.JAXWSTransport.getUDDISecurityService(JAXWSTransport.java:104)
at org.apache.juddi.v3.client.transport.Transport.getUDDISecurityService(Transport.java:43)
Similar exception for Inquiry service, replication service, etc.
In org.apache.juddi.v3.client.transport.JAXWSTransport.java file there are constants with service names which differ from service names in jboss-as/server/<profile>/deploy/juddiv3.war/WEB-INF/wsdl/esb*.wsdl files
- incorporates
-
SOA-2329 juddi webservice wsdl needs to correct service names
-
- Closed
-
- is blocked by
-
JBESB-3507 juddi webservice service names now differ from those expected by JAXWSTransport
-
- Closed
-
- is related to
-
SOA-1922 Unable to retreive services using jUDDI client with JAXWSTransport.
-
- Closed
-
- relates to
-
SOA-3164 Juddi client cannot retrieve services with JAXWSTransport
-
- Closed
-