[
https://issues.apache.org/jira/browse/AXIS2-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-3363.
-------------------------------------------------
Resolution: Fixed
There was an issue in axis2 with the namespace handling of parts imported from
the other wsdls. I have fixed this some time ago.
Please check whether this exception is occur with a current trunk build and if
so please attach your wsdl. Then we will be able to have a look at.
> Target Java Namespace of Faults is extracted from Port Type, not Message.
> -------------------------------------------------------------------------
>
> Key: AXIS2-3363
> URL: https://issues.apache.org/jira/browse/AXIS2-3363
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.3
> Environment: Ubuntu Gutsy
> Reporter: Scott S. McCoy
>
> Defining a message in one namespace, and importing and reusing that message
> as a soap fault, results in the fault itself being generated in the message
> of the port type. This defeats the purpose of using this approach to
> defining your faults. It's impossible to import wsdl:faults into a port
> type, and such, it's unreasonable to operate this way as it eliminates the
> ability to reuse fault definitions.
> java exceptions representing faults should be defined in the namespace of the
> message used for the fault. This way the fault name will not have to be
> fully qualified if say, six different services throw an AccessDeniedFault
> which is otherwise identical.
--
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: [email protected]
For additional commands, e-mail: [email protected]
