Bug 780060 (SOA-2425) - Juddi client cannot retrieve services with JAXWSTransport
Summary: Juddi client cannot retrieve services with JAXWSTransport
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2425
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: jUDDI - within SOA
Version: 5.1.0.ER2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0 GA
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-14 12:41 UTC by Jiri Sedlacek
Modified: 2015-08-02 23:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-13 06:46:32 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779546 0 urgent CLOSED Unable to retreive services using jUDDI client with JAXWSTransport. 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 780712 0 high CLOSED Juddi client cannot retrieve services with JAXWSTransport 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-2425 0 Major Closed Juddi client cannot retrieve services with JAXWSTransport 2012-11-05 19:02:12 UTC

Internal Links: 779546 780712

Description Jiri Sedlacek 2010-10-14 12:41:35 UTC 
Link type: Superset, Source: SOA-2425, Destination: SOA-2329
project_key: SOA

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
Comment 1 Jiri Sedlacek 2010-10-14 12:42:07 UTC 
Link: Added: This issue is related to SOA-1922
Comment 2 Kevin Conner 2010-10-14 13:02:24 UTC 
This is related to JBESB-3479
Comment 3 Kevin Conner 2010-10-14 13:50:37 UTC 
I have double checked this with the current code and we are using the correct name as defined by juddi.  I'll have to dig deeper into this and see where the fault lies.
Comment 4 Kevin Conner 2010-10-14 13:54:53 UTC 
There is a mismatch between the juddi JAXWSTransport, which tries to obtain a service with the name UDDI_Security_Port, and the java annotation in UDDISecurityImpl which defines a service with the name UDDISecurityService.

We currently override the implementation but we define the same service name as that class.  I'll check the Oasis WSDL later to see which is correct.
Comment 5 Kevin Conner 2010-10-15 10:31:23 UTC 
Link: Added: This issue depends JBESB-3507
Comment 6 Kevin Conner 2010-10-15 10:34:38 UTC 
I have reverted the WSDL service names and changed the annotations to match.
Comment 7 Laura Bailey 2010-12-17 00:41:24 UTC 
Writer: Added: Darrin
Comment 8 Laura Bailey 2010-12-17 00:47:56 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Comment 10 Jiri Sedlacek 2011-02-07 11:57:50 UTC 
verified in 5.1.0.ER9
Comment 11 Kevin Conner 2011-02-08 15:10:52 UTC 
Link: Added: This issue incorporates SOA-2329
Comment 12 Laura Bailey 2011-02-13 06:38:37 UTC 
Reopening to add release note text. Will set back to Closed -> Done shortly.
Comment 13 Laura Bailey 2011-02-13 06:46:32 UTC 
Setting to Closed -> Done after adding a release note.
Comment 14 Laura Bailey 2011-02-13 06:46:32 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: The jUDDI client could not retrieve services with the JAXWSTransport. Any attempt resulted in an exception of type TransportException. This occurred because the service names specified in the WSDL did not match those in the JAXWSTransport. The WSDL has been updated to match the JAXWSTransport.
Comment 15 Len DiMaggio 2011-07-12 23:42:22 UTC 
Link: Added: This issue relates to SOA-3164
Note You need to log in before you can comment on or make changes to this bug.