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 "trebor iksrazal (JIRA)" <ji...@apache.org> on 2006/02/07 15:36:57 UTC
[jira] Created: (AXIS2-434) SOAPMonitor ported to axis2
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
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
Re: [jira] Commented: (AXIS2-434) SOAPMonitor ported to axis2
Posted by robert lazarski <ro...@gmail.com>.
Thanks Ajith .
Robert
http://www.braziloutsource.com
On 4/18/06, Ruchith Udayanga Fernando (JIRA) <ji...@apache.org> wrote:
>
> [
> http://issues.apache.org/jira/browse/AXIS2-434?page=comments#action_12374847]
>
> Ruchith Udayanga Fernando commented on AXIS2-434:
> -------------------------------------------------
>
> Ajith just fixed it !
> SVN revision 394836
>
> > 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
>
>
[jira] Updated: (AXIS2-434) SOAPMonitor ported to axis2
Posted by "trebor iksrazal (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-434?page=all ]
trebor iksrazal updated AXIS2-434:
----------------------------------
Attachment: soapmonitor.zip
Here's the source. I tried to fit it to the axis2 package structure.
> 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
> Attachments: 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
[jira] Commented: (AXIS2-434) SOAPMonitor ported to axis2
Posted by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-434?page=comments#action_12374847 ]
Ruchith Udayanga Fernando commented on AXIS2-434:
-------------------------------------------------
Ajith just fixed it !
SVN revision 394836
> 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
[jira] Updated: (AXIS2-434) SOAPMonitor ported to axis2
Posted by "trebor iksrazal (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-434?page=all ]
trebor iksrazal updated AXIS2-434:
----------------------------------
Attachment: soapmonitor.zip
Please use this zip - found a small problem.
> 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
> 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
[jira] Resolved: (AXIS2-434) SOAPMonitor ported to axis2
Posted by "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
[jira] Commented: (AXIS2-434) SOAPMonitor ported to axis2
Posted by "Dennis Sosnoski (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-434?page=comments#action_12374844 ]
Dennis Sosnoski commented on AXIS2-434:
---------------------------------------
This breaks the build under JDK 1.4.X, with "package javax.xml.namespace" does not exist and "cannot resolve symbol QName" (referenced in SOAPMonitorHandler). I assume this is a missing dependency issue for the maven build.
> 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
[jira] Commented: (AXIS2-434) SOAPMonitor ported to axis2
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-434?page=comments#action_12372506 ]
Davanum Srinivas commented on AXIS2-434:
----------------------------------------
Robert,
Do you want to apply the patch yourself :)
thanks,
dims
> 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
> 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