axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Dick (JIRA)" <>
Subject [jira] Updated: (AXISCPP-553) WSDL2Ws can't generate code for inquire_v2.wsdl
Date Thu, 17 Mar 2005 11:28:20 GMT
     [ ]

Adrian Dick updated AXISCPP-553:

    Attachment: UDDI.wsdl

As has been commented, the official UDDI wsdl doesn't contain a service definition.
This is primarily because it provides the definition of implementation, but each provider
needs to supply the server details.

What we should do here is create our own WSDL, which imports the inquire_v2.wsdl, and define
a new service which uses that wsdl.  I attach an example of one I have just created.

Keeping the official UDDI wsdl unchanged, and modifying test.list to use the attached WSDL
file results in a compiling and executable stub.

> WSDL2Ws can't generate code for inquire_v2.wsdl
> -----------------------------------------------
>          Key: AXISCPP-553
>          URL:
>      Project: Axis-C++
>         Type: Bug
>   Components: Client - Stub
>     Reporter: Manohar
>     Priority: Critical
>  Attachments: UDDI.wsdl
> WSDL2Ws tool can't generate the code for an official verions of inquire_v2.wsdl.
> When run against the wsdl, WSDLWs generates the following exception.
> 16-Mar-2005 10:22:12 org.apache.axis.utils.JavaUtils isAttachmentSupported
> WARNING: Unable to find required classes (javax.activation.DataHandler and javax
> .mail.internet.MimeMultipart). Attachment support is disabled.
> org.apache.axis.wsdl.wsdl2ws.WrapperFault: the service does not exists
>         at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.getServiceEntry(Unknown Source)
>         at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.perprocess(Unknown Source)
>         at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.generateWrappers(Unknown Source)
>         at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main(Unknown Source)
> Code generation failed. Please see errors above.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message