[ 
http://issues.apache.org/jira/browse/AXIS2-1311?page=comments#action_12442501 ] 
            
Thilo Frotscher commented on AXIS2-1311:
----------------------------------------


Yes, it's fixed. Thanks.


> WSDL2Java removes fault information from WSDL file
> --------------------------------------------------
>
>                 Key: AXIS2-1311
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1311
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.1
>         Environment: Axis2 1.1 Snapshot of 02 Oct 2006
>            Reporter: Thilo Frotscher
>            Priority: Blocker
>         Attachments: hotel.wsdl, hotel.xsd
>
>
> This bug relates to the resources files that are created by WSDL2Java.
> First of all, I wonder why WSDL2Java generates a completely new WSDL file at 
> all. If it's just for adding bindings, these could be inserted into a copied 
> source WSDL. I also don't understand why the filenames of WSDL and XSDs are 
> changed.
> The actual bug I'd like to report is as follows: 
> When generating code using WSDL2Java from a WSDL that contains 
> - fault messages
> - <wsdl:fault> elements as children of <operation>
> - <wsdl:fault> elements as children of <binding>
> all these elements related to faults are missing in the generated WSDL file 
> which can be found in the resources folder. This is a severe problem, because 
> it is this generated WSDL file that is delivered in case of requests to 
> htp://...?wsdl.
> The generated code works fine though, including the exceptions that are 
> raised etc.
>  

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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to