| Author |
wsdlexception unable to determine namespace faultCode=UNBOUND_PREFIX
|
sreenivas jeenor
Ranch Hand
Joined: Jan 09, 2005
Posts: 125
|
|
Hi All, I want to use third party web service provided by the vendor. When the i run the WSDL2Java command ,i am getting the following error which i could not configure. where as the same wsdl file is working in .net framework I have included all the jar files required for it. i.e axis.jar,commons-discovery-0.2.jar,commons-logging-1.0.4.jar,jaxrpc.jar,log4j-1.2.8.jar,saaj.jar,wsdl4j-1.5.1.jar. error is ------------------------------ C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\ws-axis>java org.apache.axis.wsdl.WSDL2Java https://wsvar.paymentech.net/PaymentechGateway/wsdl/PaymentechGateway.wsdl WSDLException (at /definitions/message[1]/part): faultCode=UNBOUND_PREFIX: Unabl e to determine namespace of 'ns:NewOrder'.: at com.ibm.wsdl.util.xml.DOMUtils.getQName(Unknown Source) at com.ibm.wsdl.util.xml.DOMUtils.getQualifiedAttributeValue(Unknown Sou rce) at com.ibm.wsdl.xml.WSDLReaderImpl.getQualifiedAttributeValue(Unknown So urce) at com.ibm.wsdl.xml.WSDLReaderImpl.parsePart(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseMessage(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav a:516) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav a:495) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) at java.lang.Thread.run(Thread.java:595) ------------------------------------- Help me sreenivas
|
 |
Peer Reynders
Bartender
Joined: Aug 19, 2005
Posts: 2906
|
|
Originally posted by sreenivas jeenor: where as the same wsdl file is working in .net framework
The WSDL isn't correct just because one tool can successfully consume the WSDL. It may be that that particular WSDL code generator is perfectly happy to differentiate elements by their prefix - but it doesn't verify that the namespace prefix actually has a URI assigned (which becomes important once you import or include outside XML schemas).
Basically it is saying that in the <part> element of the first <message> element in the WSDL "ns:NewOrder" is being used and that the namespace prefix "ns" hasn't been assigned a namespace URI. So its saying the something like xmlns:ns="http://www.theirnamespaceuri.com/service/category" should be in but isn't (though there are other ways
|
"Don't succumb to the false authority of a tool or model. There is no substitute for thinking."
Andy Hunt, Pragmatic Thinking & Learning: Refactor Your Wetware p.41
|
 |
J Milton
Greenhorn
Joined: Oct 16, 2007
Posts: 1
|
|
|
Try setting the name space to http://ws.paymenttech.net/PaymentechGateway/ That worked for me.
|
 |
 |
|
|
subject: wsdlexception unable to determine namespace faultCode=UNBOUND_PREFIX
|
|
|