You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2007/06/29 13:59:05 UTC
[jira] Resolved: (AXIS2-2792) Java2WSDL is oddly naming WSDL faults
[ https://issues.apache.org/jira/browse/AXIS2-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-2792.
--------------------------------------
Resolution: Fixed
fixed in current SVN
Revision: 551859
> Java2WSDL is oddly naming WSDL faults
> -------------------------------------
>
> Key: AXIS2-2792
> URL: https://issues.apache.org/jira/browse/AXIS2-2792
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: wsdl
> Reporter: Glen Daniels
> Assignee: Deepal Jayasinghe
> Priority: Blocker
> Fix For: 1.3
>
>
> If we have
> package ns;
> class Service {
> void foo(int i) throws CustomException {
> }
> void bar(int i) throws CustomException {
> }
> }
> Java2WSDL currently generates two separate fault messages:
> <message name="fooFault0">
> <message name="barFault1">
> Both of those refer to <part element="ns:CustomException">
> We should be generating a single message which gets referred to by both methods, just like the exception is used by both methods.
> <message name="CustomException">
> Deepal is working on this.
--
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.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org