[jira] Resolved: (AXIS2-434) SOAPMonitor ported to axis2

["robert lazarski (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/AXIS2-434?page=all ]
     
robert lazarski resolved AXIS2-434:
-----------------------------------

    Fix Version: 1.0
     Resolution: Fixed

Commited to svn. The approach was discussed on the dev list here: 

http://marc.theaimsgroup.com/?l=axis-dev&m=114527481628117&w=2

#3 was not implemented - the user needs to copy the applet classes to axis2/*.class/WEB-INF . 

> SOAPMonitor ported to axis2
> ---------------------------
>
>          Key: AXIS2-434
>          URL: http://issues.apache.org/jira/browse/AXIS2-434
>      Project: Apache Axis 2.0 (Axis2)
>         Type: New Feature

>   Components: Tools
>     Versions: 0.94
>  Environment: Linux, java 5.0 , mozilla
>     Reporter: trebor iksrazal
>      Fix For: 1.0
>  Attachments: soapmonitor.zip, soapmonitor.zip
>
> The soap monitor is really three components: An applet which displays responses / requests, a servlet which binds to a default port of 5001 and connects to the applet, and a handler used to intercept the soap messages. Therefore it requires three diferent pieces to be installed: applet classes --> *.class/WEB-INF, a servlet config in web.xml and the servlet classes in WEB-INF/lib etc, and a module with the handlers under WEB-INF/modules. The module also requires phases defined and placed in axis2.xml .   
> Accordingly, I tried to fit these classes into a structure that matches axis2. The source files are under the directory --> modules/soapmonitor .  I did some guess work here as a starting point. 
> Not needed but perhaps helpful is my build.xml along with my web.xml and axis2.xml, under the dir 'resources'in the zip file. 
> The only needed change in the port - besides package name changes - was the SOAPMonitorHandler. A module was created with phase orders, and the handler determines whether the soap message is a request or a response by MessageContext.getFlow(). The axis 1.x soap handler depended on MessageContext.isResponseWritten() . However,  setResponseWritten() is never invoked in the axis2 code base. 
> Attachment comming in comments. 

-- 
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