| Summary: | Juddi client cannot retrieve services with JAXWSTransport | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Sedlacek <jsedlace> |
| Component: | jUDDI - within SOA | Assignee: | Kevin Conner <kevin.conner> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.1.0.ER2 | CC: | oskutka |
| Target Milestone: | --- | ||
| Target Release: | 5.1.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2425 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-02-13 06:46:32 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Link: Added: This issue is related to SOA-1922 This is related to JBESB-3479 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. 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. Link: Added: This issue depends JBESB-3507 I have reverted the WSDL service names and changed the annotations to match. Writer: Added: Darrin Release Notes Docs Status: Added: Not Yet Documented verified in 5.1.0.ER9 Link: Added: This issue incorporates SOA-2329 Reopening to add release note text. Will set back to Closed -> Done shortly. Setting to Closed -> Done after adding a release note. 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. Link: Added: This issue relates to SOA-3164 |
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