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 "Scott S. McCoy (JIRA)" <ji...@apache.org> on 2007/11/24 01:32:43 UTC

[jira] Created: (AXIS2-3363) Target Java Namespace of Faults is extracted from Port Type, not Message.

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: Axis 2.0 (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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org