[
https://issues.apache.org/jira/browse/AXIS2-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518593
]
robert lazarski commented on AXIS2-3107:
----------------------------------------
The soap monitor just does messageContext.getEnvelope().toString() . There are
some things - MTOM for example - that the soap monitor currently can't capture
right and REST may fall into that category. You could help us track this down
by using TCPMon to see if the same behavior occurs there as well.
> REST & SOAP Monitor inconsistency
> ---------------------------------
>
> Key: AXIS2-3107
> URL: https://issues.apache.org/jira/browse/AXIS2-3107
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Axis2-1.3-RC2
> Tomcat 5.5
> Linux
> Reporter: simishag
> Priority: Minor
> Fix For: 1.3
>
>
> When debugging with the SOAP Monitor applet, REST requests don't appear to
> work right. I discovered this while working on another issue, and some more
> detail on reproducing this can be found in issue AXIS2-3106.
> As I understand it, REST requests are processed by Axis into actual SOAP
> requests, and the resulting requests can be viewed in the SOAP Monitor. I
> tried 3 different method/parameter combinations, each with 1 invalid
> parameter name. All 3 of these combinations resulted in identical SOAP
> requests when viewed in the monitor, with 2 parameters set properly and the
> 3rd invalid parameter missing, as expected. However, although the monitor
> shows identical SOAP requests, the requests are not in fact being delivered
> to Axis in this manner, which is verified by the 3 very different error
> responses I observed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
