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 bu...@apache.org on 2003/07/01 16:17:51 UTC
DO NOT REPLY [Bug 15126] -
onFault on global Handlers are not called...
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15126>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15126
onFault on global Handlers are not called...
------- Additional Comments From vladumansky@yahoo.com 2003-07-01 14:17 -------
vladumansky@yahoo.com:
Steps to reproduce:
1. Insert a handler into both requestFlow and responseFlow of a
globalConfiguration
<requestFlow>
<handler type="java:org.apache.axis.handlers.JWSHandler">
<parameter name="scope" value="session"/>
</handler>
<handler type="java:org.apache.axis.handlers.JWSHandler">
<parameter name="scope" value="request"/>
<parameter name="extension" value=".jwr"/>
</handler>
<handler name="TestHandler" type="java:org.apache.axis.handlers.JAXRPCHandler">
<parameter name="className" value="SomeTestHandler"/>
<parameter name="scope" value="request"/>
</handler>
</requestFlow>
<responseFlow>
<handler name="TestHandler" type="java:org.apache.axis.handlers.JAXRPCHandler">
<parameter name="className" value="SomeTestHandler"/>
<parameter name="scope" value="request"/>
</handler>
</responseFlow>
2. Invoke a service on the same axis engine that causes a fault to occur
3. Notice that onFault method of the TestHandler is not being invoked
4. If the TestHandler is moved out of the GlobalChain and into the
request/response flow of the service, the method is being called