Bug 780712 (SOA-3164) - Juddi client cannot retrieve services with JAXWSTransport
Summary: Juddi client cannot retrieve services with JAXWSTransport
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3164
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: jUDDI - within SOA
Version: 5.2.0dev2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: tcunning
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-12 23:41 UTC by Len DiMaggio
Modified: 2011-11-15 18:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
5.2 Dev2 build (with jUDDI 3.1.0)
Last Closed: 2011-11-15 18:21:10 UTC
Type: Bug

Attachments (Terms of Use)
simple-publish.zip (73.71 KB, application/zip)
2011-07-12 23:41 UTC, Len DiMaggio 		no flags Details
simple_publish-fixed.zip (70.08 KB, application/zip)
2011-07-14 15:25 UTC, tcunning 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 780060 0 high CLOSED Juddi client cannot retrieve services with JAXWSTransport 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-3164 0 Major Closed Juddi client cannot retrieve services with JAXWSTransport 2012-11-05 19:02:34 UTC

Internal Links: 780060

Description Len DiMaggio 2011-07-12 23:41:36 UTC 
Steps to Reproduce: Run the jUDDI sample app - see attached .zip file.

project_key: SOA

The problem first reported in https://issues.jboss.org/browse/SOA-2425 and resolved for 5.1 GA is back in 5.2 Dev2.


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
publish
	at org.apache.juddi.v3.client.transport.JAXWSTransport.getUDDISecurityService(JAXWSTransport.java:104)
	at org.apache.juddi.v3.client.transport.Transport.getUDDISecurityService(Transport.java:43)
	at org.apache.juddi.example.publish.SimplePublish.<init>(SimplePublish.java:43)
	at org.apache.juddi.example.publish.SimplePublish.main(SimplePublish.java:122)
Caused by: javax.xml.ws.WebServiceException: {urn:uddi-org:v3_service}UDDI_Security_Port is not a valid service. Valid services are: {urn:uddi-org:v3_service}UDDISecurityService
	at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:230)
	at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:175)
	at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:104)
	at javax.xml.ws.Service.<init>(Service.java:76)
	at javax.xml.ws.Service.create(Service.java:700)
	at org.apache.juddi.v3.client.transport.JAXWSTransport.getUDDISecurityService(JAXWSTransport.java:101)
	... 3 more
java.lang.NullPointerException
	at org.apache.juddi.example.publish.SimplePublish.publish(SimplePublish.java:62)
	at org.apache.juddi.example.publish.SimplePublish.main(SimplePublish.java:123)
Comment 1 Len DiMaggio 2011-07-12 23:41:56 UTC 
Attachment: Added: simple-publish.zip
Comment 2 Len DiMaggio 2011-07-12 23:42:22 UTC 
Link: Added: This issue is related to SOA-2425
Comment 3 Kevin Conner 2011-07-13 08:49:07 UTC 
This is different from SOA-2425 as we are now using the jUDDI webservice endpoints and not the ESB provided ones.  It looks like we may have to reintroduce our endpoints.
Comment 4 tcunning 2011-07-14 15:25:11 UTC 
Attachment: Added: simple_publish-fixed.zip
Comment 5 tcunning 2011-07-14 15:27:24 UTC 
Works on dev2.     Two changes : 

- in the pom.xml, change the juddi version from 3.0.4 to 3.1.0
- in the uddi.xml, change the endpoints to match what jbossws reports (for example, http://127.0.0.1:8080/juddiv3/services/inquiry rather than http://127.0.0.1:8080/juddiv3/services/inquiry?wsdl)

I also the maven exec plugin into the test to make it easier to run (mvn exec:exec).
Comment 6 tcunning 2011-07-14 15:28:38 UTC 
The fixes above went into the simple_publish test (uploaded a simple_publish-fixed.zip with the changes).
Note You need to log in before you can comment on or make changes to this bug.