Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <24802513.1153991594297.JavaMail.jira@brutus>
Date: Thu, 27 Jul 2006 02:13:14 -0700 (PDT)
From: "David Illsley (JIRA)" <jira@apache.org>
To: axis-dev@ws.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
In-Reply-To: <21199862.1149081450764.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/AXIS2-789?page=comments#action_12423802 ] 
            
David Illsley commented on AXIS2-789:
-------------------------------------

Well that line is the important one....

I agree that most web services start from a WSDL, with operations and associated MEPs. What I disagree with is the idea the the MEPs implemented by Axis2 are the only possible MEPs or that they are the only possible way that they can be implemented. I agree that an inbound message with a RelatesTo may be part of a request-response MEP, it's just that it started outside of Axis2 and may be triggering (or be a part of) a new MEP too.

I disagree that this in any way introduces statefulness beyond that which axis2 already has. It simply enables the same state to be managed differently. Instead of it being held in an in-memory AxisOperation object it canbe stored away and retrieved which is far preferable for very long-running exchanges. (In terms of introducing statefulness reference parameters are far more guilty anway.... WS-RF anyone?)

Anyway, as you said this has been discussed on the list. If you want to continue the discussion I suggest we move back there.
David

> 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