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 "Jeff Saremi (JIRA)" <ax...@ws.apache.org> on 2005/11/23 17:38:38 UTC
[jira] Created: (AXIS-2317) Provide Extensions so that Raw Messages can be captured or logged
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
[jira] Commented: (AXIS-2317) Provide Extensions so that Raw Messages can be captured or logged
Posted by "Jeff Saremi (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2317?page=comments#action_12358664 ]
Jeff Saremi commented on AXIS-2317:
-----------------------------------
I'm interested in the production-time beahvior. I was checking out HTTPSender and it looks like this is where one can examine the incoming and outgoing streams. There's also a relatively easy way to overwrite this class and provide our own in the client's deployment xml. But there's so much logic in this code and they're all nested in big, private methods that would make the override such as big task.
> 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
[jira] Commented: (AXIS-2317) Provide Extensions so that Raw Messages can be captured or logged
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ 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
[jira] Commented: (AXIS-2317) Provide Extensions so that Raw Messages can be captured or logged
Posted by "Jayachandra Sekhara Rao Sunkara (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2317?page=comments#action_12358645 ]
Jayachandra Sekhara Rao Sunkara commented on AXIS-2317:
-------------------------------------------------------
Doesn't the TCPMon (org.apache.axis.utils.tcpmon) tool accomplish the need on client side?
Though its not wise to find a place for TCPMon in a production setup (connection resets after a few fifty requests), but for debugging and analyiis purposes it does exactly what you are asking for.
> 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
[jira] Commented: (AXIS-2317) Provide Extensions so that Raw Messages can be captured or logged
Posted by "Jeff Saremi (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2317?page=comments#action_12358464 ]
Jeff Saremi commented on AXIS-2317:
-----------------------------------
I think Filters would solve the problem on the server.
Is there anything similar for the SOAP Client piece?
> 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