[ http://issues.apache.org/jira/browse/AXIS2-1564?page=all ]
Deepal Jayasinghe updated AXIS2-1564:
-------------------------------------
Priority: Blocker (was: Critical)
> Incoming SOAPFault on client side flows though InFlow *and* InFaultFlow
> -----------------------------------------------------------------------
>
> Key: AXIS2-1564
> URL: http://issues.apache.org/jira/browse/AXIS2-1564
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.1
> Environment: Axis2 1.1 Snapshot of 29 Oct
> Reporter: Thilo Frotscher
> Assigned To: Deepal Jayasinghe
> Priority: Blocker
>
> I created a module with a simple log handler that just logs a message. Using
> a client repository, I engaged this module globally for my client
> application. For testing purposes the handler was configured to be included
> into InFlow (PreDispatch), OutFlow (MessageOut), InFaultFlow (PreDispatch)
> and OutFaultFlow (MessageOut).
> When the client application receives a SOAP fault from a service, two log
> handlers are invoked: the handler in InFlow and the handler in InFaultFlow,
> i.e. incoming SOAP faults flow through both flows on the client side. It is
> my understanding that incoming messages containing faults should flow through
> InFaultFlow *only*, but not through InFlow.
>
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
