You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Erik Godding Boye (JIRA)" <ax...@ws.apache.org> on 2006/03/09 13:31:54 UTC

[jira] Commented: (AXIS-2429) Invalid WSDL created

    [ http://issues.apache.org/jira/browse/AXIS-2429?page=comments#action_12369633 ] 

Erik Godding Boye commented on AXIS-2429:
-----------------------------------------

When I run the generated JUnit test case that tests getting the WSDL file from the server (TicketCentralTestCase#testTicketCentralSoapWSDL), I get the following error:
javax.xml.rpc.ServiceException: Error processing WSDL document:  
WSDLException (at /wsdl:definitions/types): faultCode=INVALID_WSDL: Encountered illegal extension element 'types' in the context of a 'javax.wsdl.Definition'. Extension elements must be in a namespace other than WSDL's.: 
	at org.apache.axis.client.Service.initService(Service.java:249)
	at org.apache.axis.client.Service.<init>(Service.java:164)
	at org.apache.axis.client.ServiceFactory.createService(ServiceFactory.java:198)

> Invalid WSDL created
> --------------------
>
>          Key: AXIS-2429
>          URL: http://issues.apache.org/jira/browse/AXIS-2429
>      Project: Apache Axis
>         Type: Bug
>     Versions: 1.2, 1.2.1, 1.3
>     Reporter: Erik Godding Boye
>     Priority: Minor
>  Attachments: TicketCentralSoap_gen.wsdl, TicketCentralSoap_orig.wsdl
>
> The WSDL created by Axis for my deployed services is invalid. It seems like the problem is related to namespace missing from nested elements in the WSDL. I will attach the original WSDL and the created/generated WSDL files to this issue.
> My workaround is to include the origianl WSDL file in my deployment and modifiy the generated Axis deploy file (ticketcentral.wsdl.deploy.wsdd) to refer the original WSDL. This is done by adding the following line to the deploy file:
> <wsdlFile>/TicketCentralSoap_orig.wsdl</wsdlFile>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira