[
https://issues.apache.org/jira/browse/AXIS2-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492491 ]
Jorge Fernández commented on AXIS2-2325:
----------------------------------------
Also, one more thing:
In the message definition, the prefix of the faults is wrong, it should be the prefix of the service schema namespace and it's the prefix of the faults namespace.
In the file I sent is:
<wsdl:message name="DataAccessFault">
<wsdl:part name="part1" element="ax21:DataAccessFault" />
</wsdl:message>
and it should be
<wsdl:message name="DataAccessFault">
<wsdl:part name="part1" element="xsd:DataAccessFault" />
</wsdl:message>
I attached new exceptions. I forgot that I had changed their names. The new exceptions are DataAccessFault and ValidationFault
> Java2WSDL does not generate faults correctly
> --------------------------------------------
>
> Key: AXIS2-2325
> URL:
https://issues.apache.org/jira/browse/AXIS2-2325
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.1.1
> Environment: Windows XP Java 1.5, Eclipse 3.2.2, Axis2 Eclipse Plugin 1.2.1
> Reporter: Jorge Fernández
> Assigned To: Deepal Jayasinghe
> Attachments: API.java, API.java, API.wsdl, API.wsdl, API.wsdl, API.wsdl, axis2-2325patch.txt, DataAccessFault.java, IncorrectPasswordFault.java, IncorrectUserFault.java, ValidationFault.java
>
>
> The first problem is that in the WSDL generated my fault name is ignored and instead it's compound from the operation name and "Fault".
> Also if I throw two exceptions from one operation, in the WSDL only one appears and with the name I said before.
> I attach the API from where I build the WSDL, the Faults classes and the WSDL generated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail:
axis-dev-unsubscribe@ws.a...
For additional commands, e-mail:
axis-dev-help@ws.a...
opensubscriber is not affiliated with the authors of this message nor responsible for its content.