You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@axis.apache.org by "Fred Preston (JIRA)" <ax...@ws.apache.org> on 2005/10/04 11:56:48 UTC

[jira] Updated: (AXISCPP-248) WSDL2WS creates header files that are empty or never used

     [ http://issues.apache.org/jira/browse/AXISCPP-248?page=all ]

Fred Preston updated AXISCPP-248:
---------------------------------

    Attachment: EmptyHeader.wsdl
                myBAT.xsd

Hi Chinthana,
I've included a simple WSDL and XSD that demonstrate the 'empty header file' problem.  The reason it was first introduced was because the classes will include all sub classes regardless of use and so what is happening is that some unused or empty classes where not being created but still being included and so the compile would fail because of missing include files.  The simple way to 'fix' this was to ensure that all classes produced header files.  The real solution is to make the logic that decides what files to include better so it knows not to include emply classes and so these files do not need to be generated.

> WSDL2WS creates header files that are empty or never used
> ---------------------------------------------------------
>
>          Key: AXISCPP-248
>          URL: http://issues.apache.org/jira/browse/AXISCPP-248
>      Project: Axis-C++
>         Type: Bug
>   Components: WSDL processing - RPC, WSDL processing - Doc
>     Versions: current (nightly)
>  Environment: n/a
>     Reporter: Fred Preston
>      Fix For: 1.6 Alpha
>  Attachments: EmptyHeader.wsdl, myBAT.xsd
>
> When the WSDL imports an XSD, C++ code gets generated for all the types in the XSD, not just the types which are actually used in the WSDL 

-- 
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