axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eran Chinthaka (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-789) A SOAPFault targeted at a service (e.g. using WS-Addressing FaultTo) is not passed to the service object
Date Thu, 27 Jul 2006 08:34:14 GMT
    [ http://issues.apache.org/jira/browse/AXIS2-789?page=comments#action_12423800 ] 
            
Eran Chinthaka commented on AXIS2-789:
--------------------------------------

Hi,

+1 for the patch, except for the if (null == msgContext.getRelatesTo() || !(this instanceof
OutInAxisOperation))  part in AxisOperation.java.
I think its incorrect if you do not throw an error here. I know there was a thread on this,
but let me explain what I feel. 
Web services normally starts from a WSDL. It defines operations and operations have MEPs and
messages. So messages have something to do with a MEP. Even though WS-A doesn't define anything
about the content of the relatesTo, I feel its a hole in the spec itself. What I feel is,
a message better not contain a relatesTo value which has a message id of a message which is
not in the current MEP. 
One more point, web services. by definition are stateless. If we let this message to refer
to a message outside the MEP, then I feel its an attempt to have some statefulness. 

-- Chinthaka

> A SOAPFault targeted at a service (e.g. using WS-Addressing FaultTo) is not passed to
the service object
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-789
>                 URL: http://issues.apache.org/jira/browse/AXIS2-789
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: core
>            Reporter: David Illsley
>         Assigned To: Deepal Jayasinghe
>            Priority: Minor
>         Attachments: patch.txt, patch2.txt, patch3.txt
>
>
> A SOAPFault targeted at a service (e.g. using WS-Addressing FaultTo) is not passed to
the service object. It currently passes the message through the InFaultFlow and then processing
stops. This prevents Axis2 from being used to host a 'FaultTo' service which processes faults
generated in other services.
> I have copied the invocation code from AxisEngine.receive() to AxisEngine.receiveFault()
and all unit tests continue to pass as well as allowing the fault to be propagated to the
service object.
> Patch to follow momentarily

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message