Hi Kurt,
I changed following lines in class JAXWSTransport.java:
//FS: added constant
public final static String INQUIRY_SERVICE_NAME = "UDDI_Service";
public UDDIInquiryPortType getUDDIInquiryService(String endpointURL) throws
TransportException {
if (inquiryService==null) {
try {
. . .
QName qName = new QName(UDDI_V3_SERVICE_NAMESPACE, INQUIRY_SERVICE);
//FS: defined new QName for Service creation: with "UDDI_Service" instead
of "UDDI_Inquiry_Port";
QName qNameService = new QName(UDDI_V3_SERVICE_NAMESPACE,
INQUIRY_SERVICE_NAME);
Service service = Service.create(new URL(endpointURL), qNameService);
//FS: pass qName explicitly for Port constructor
inquiryService = (UDDIInquiryPortType) service.getPort(qName,
UDDIInquiryPortType.class);
//old: inquiryService = (UDDIInquiryPortType)
service.getPort(UDDIInquiryPortType.class);
. . .
}
From: Kurt T Stam [mailto:kurt.s...@gmail.com]
Sent: Freitag, 27. August 2010 14:34
To: juddi-user@ws.apache.org
Subject: Re: JUDDI WSDL files
On 8/27/10 6:27 AM, Strickstrock, Frank wrote:
Hi,
I am trying to connect a Jaxws Client to a Microsoft UDDI. As the server does
not provide the WSDL I tried the packaged files in "uddi-ws-3.0.3-sources.jar"
When trying to initialize the service and port I get following error msg:
org.apache.juddi.v3.client.transport.TransportException:
{urn:uddi-org:v3_service}UDDI_Inquiry_Port is not a valid service. Valid
services are: {urn:uddi-org:v3_service}UDDI_Service
at
org.apache.juddi.v3.client.transport.JAXWSTransport.getUDDIInquiryService(JAXWSTransport.java:86)
at
org.apache.juddi.v3.client.transport.Transport.getUDDIInquiryService(Transport.java:40)
at juddi.HalloWorld.<init>(HalloWorld.java:42)
at juddi.HalloWorld.main(HalloWorld.java:208)
Caused by: javax.xml.ws.WebServiceException:
{urn:uddi-org:v3_service}UDDI_Inquiry_Port is not a valid service. Valid
services are: {urn:uddi-org:v3_service}UDDI_Service
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>(Unknown Source)
at javax.xml.ws.Service.create(Unknown Source)
at
org.apache.juddi.v3.client.transport.JAXWSTransport.getUDDIInquiryService(JAXWSTransport.java:83)
... 3 more
While searching at the internet I found a page with a simialre issue.
https://jira.jboss.org/browse/SOA-1922
There one person states:
Kevin Conner added a comment - 06/Feb/10 03:33 AM
Has to rejig all the WSDL to get the juddi uddi-tck tests to read, the
shipped wsdl does not appear to be correct.
To overcome the problem, I extracted and manipulated the JAXWSTransport class
plus the WSDL to match the correct namespaces.
Actually I got it running now . but I don't like this way.
Can you please advice ?
Thanks,
Frank.
Hi Frank,
Can you explain what you had to change to make it work?
Thx,
--Kurt
