[ http://issues.apache.org/jira/browse/AXIS-1963?page=comments#action_64164 ] Sergio Bossa commented on AXIS-1963: ------------------------------------
Ok dims, I've tweaked my WSDL as you suggested, and now all works fine. Yes, it should be fine to have the code fixed, but sure there are more serious bug around waiting to be fixed... So, you can close this bug report. Thanks. Sergio B. > WSDL2JAVA problems with custom exceptions > ----------------------------------------- > > Key: AXIS-1963 > URL: http://issues.apache.org/jira/browse/AXIS-1963 > Project: Axis > Type: Bug > Components: WSDL processing > Versions: 1.2RC2, 1.2RC3 > Environment: Linux > Reporter: Sergio Bossa > Attachments: LocalXQueryService.wsdl, LocalXQueryService.wsdl > > I have a custom exception coded as follows: > public class MySOAPFault extends AxisFault > { > public static final String ERROR="Error.1"; > > public MySOAPFault(String code, String message) > { > super(message); > > setFaultCodeAsString(code); > } > } > And this is its WSDL mapping: > <element name="MySOAPFault"> > <complexType> > <sequence/> > </complexType> > </element> > ... > <wsdl:message name="MySOAPFault"> > <wsdl:part element="tns:MySOAPFault" name="fault"/> > </wsdl:message> > ... > When I run WSDL2JAVA over my WSDL, I get a class named MySOAPFault_Element > (not MySOAPFault, as it should be), leading to compile time errors. > However, all works fine if I use Axis API directly, or if I use other > languages: the custom exception is correctly thrown and deserialized. -- 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
