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 "Dennis Sosnoski (JIRA)" <ji...@apache.org> on 2006/04/18 06:47:18 UTC
[jira] Commented: (AXIS2-434) SOAPMonitor ported to axis2
[ 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