[ http://issues.apache.org/jira/browse/AXIS-2317?page=comments#action_12358417 ]
Davanum Srinivas commented on AXIS-2317: ---------------------------------------- Do Servlet Filters help? - http://java.sun.com/products/servlet/Filters.html -- dims > Provide Extensions so that Raw Messages can be captured or logged > ----------------------------------------------------------------- > > Key: AXIS-2317 > URL: http://issues.apache.org/jira/browse/AXIS-2317 > Project: Apache Axis > Type: Improvement > Components: Basic Architecture > Versions: 1.2 > Reporter: Jeff Saremi > Priority: Minor > > Don't know if anyone else is sharing this problem or not but its almost > impossible to intercept/view/examine the raw messages coming to Axis or > leaving Axis (server or client both). I'm referring to messages that > can/cannot be parsed as XML therefore causing exceptions to be thrown. > While in a service or a handler we have the ability to implement our own > exception handling but before the message gets to our service or after its > left our service we have no clue as to what was recevied or sent. > I'm proposing to provide proper extension/override points at lower levels > than service and handlers i.e at AxisServlet or Call level, so that messages > can be logged (as an example of something to do with messages). I also know > that InputStream/OutputStream themselves have limitations in that you can > only read/write from/to the stream once. > If this description is not understandable pls ask me to provide more > explanation/examples instead of rejecting this defect. > thanks -- 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
