Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Hi, > I'm not completely clear on your setup but it seems to me you are > creating a ConfigurationContext yourself or are not loading the same > axis2.xml as you showed me If you create a ConfigurationContext without specifying an axis2.xml, axis2_default.xml [1] will be used and this will cause problems as the user defined phases are not present there. Anyway Axis2 is going to have dynamic phase support very soon, so these kind of problems will not occur as the modules them selves will be able to define the phases which they require to register their handlers. [1] - http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/deployment/axis2_default.xml?view=markup thanks, Nandana - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
On 4 Jan 2008, at 16:00, robert lazarski wrote: I'm not completely clear on your setup but it seems to me you are creating a ConfigurationContext yourself or are not loading the same axis2.xml as you showed me - which is why putting axis2 in debug would help as it would confirm the soapmonitorPhase is being loaded in inflow. The two configuration files (embedded and inside tomcat) are the indeed the same. Anywhich way though, what you are lacking is getting the soapmonitorPhase configured in inflow - be it via axis2.xml, ConfigurationContext etc. Are you able to engage and run the other modules like logging and ping ok in your embedded setup? Not the logging (it throws an exception saying it's not valid), but I can successfully deploy a module of mine. Can you load the phases programtically in your embedded setup? Yes. See the unit tests in the src tree for how to do phase loading programtically - sorry for being a bit vague here but looking at the source is the quickest way to tackle advance cases like this. HTH, Robert Michele On Jan 4, 2008 12:39 PM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, I get that error if I run an embedded version of axis2. If I deploy it to tomcat (clean setup) it works fine. Jan 4, 2008 3:36:45 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Jan 4, 2008 3:36:45 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1011 ms Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.14 Jan 4, 2008 3:36:46 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive axis2.war [INFO] Deploying module: addressing-1.3 [INFO] Deploying module: metadataExchange-1.3 [INFO] Deploying module: ping-1.3 [INFO] Deploying module: script-1.3 [INFO] Deploying module: soapmonitor-1.3 [INFO] script module activated [INFO] HTTP Sender starting [INFO] Deploying Web service: version.aar Jan 4, 2008 3:36:50 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Jan 4, 2008 3:36:50 PM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Jan 4, 2008 3:36:50 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/52 config=null Jan 4, 2008 3:36:50 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 5161 ms Any idea? Michele On 4 Jan 2008, at 14:50, robert lazarski wrote: Michele, can you post your entire stacktrace please? I can't match the error you get with current svn. The error you are getting indicates no soapmonitorPhase in inflow, yet your axis2.xml does have it. So sorry, no clear indication of the problem yet. You could try putting axis2 in debug to see the phases loaded, which may flush out the error by confirming the phase isn't loaded. Alternatively, try out tcpmon ;-) . Good luck, Robert On Jan 4, 2008 10:11 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, if the module is globally engaged I get the error I mentioned in my previous email. The same happens also if I "dynamically" engage the module. Michele On 4 Jan 2008, at 12:01, robert lazarski wrote: You need to engage the module. Search for: Then in the same place, add: HTH, Robert On Jan 4, 2008 8:44 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, in axis2 1.3 all the phases needed by the soap monitor module are already included. Michele On 4 Jan 2008, at 11:07, robert lazarski wrote: The exception is pretty self descriptive... show us the entire axis2.xml and maybe we can help. Robert On Jan 4, 2008 7:39 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Hi all, I can't enage the soapmonitor module under Axis2 1.3 because of the following error org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 'soapmonitorPhase' while deploying handler 'InFlowSOAPMonitorHandler'. My axis2.xml differs from the default one only because of the NIO transport listener. Any idea? Thanks, Michele --- -- -- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - -- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
I'm not completely clear on your setup but it seems to me you are creating a ConfigurationContext yourself or are not loading the same axis2.xml as you showed me - which is why putting axis2 in debug would help as it would confirm the soapmonitorPhase is being loaded in inflow. Anywhich way though, what you are lacking is getting the soapmonitorPhase configured in inflow - be it via axis2.xml, ConfigurationContext etc. Are you able to engage and run the other modules like logging and ping ok in your embedded setup? Can you load the phases programtically in your embedded setup? See the unit tests in the src tree for how to do phase loading programtically - sorry for being a bit vague here but looking at the source is the quickest way to tackle advance cases like this. HTH, Robert On Jan 4, 2008 12:39 PM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Robert, > > I get that error if I run an embedded version of axis2. If I deploy > it to tomcat (clean setup) it works fine. > > Jan 4, 2008 3:36:45 PM org.apache.coyote.http11.Http11Protocol init > INFO: Initializing Coyote HTTP/1.1 on http-8080 > Jan 4, 2008 3:36:45 PM org.apache.catalina.startup.Catalina load > INFO: Initialization processed in 1011 ms > Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardService start > INFO: Starting service Catalina > Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardEngine start > INFO: Starting Servlet Engine: Apache Tomcat/6.0.14 > Jan 4, 2008 3:36:46 PM org.apache.catalina.startup.HostConfig deployWAR > INFO: Deploying web application archive axis2.war > [INFO] Deploying module: addressing-1.3 > [INFO] Deploying module: metadataExchange-1.3 > [INFO] Deploying module: ping-1.3 > [INFO] Deploying module: script-1.3 > [INFO] Deploying module: soapmonitor-1.3 > [INFO] script module activated > [INFO] HTTP Sender starting > [INFO] Deploying Web service: version.aar > Jan 4, 2008 3:36:50 PM org.apache.coyote.http11.Http11Protocol start > INFO: Starting Coyote HTTP/1.1 on http-8080 > Jan 4, 2008 3:36:50 PM org.apache.jk.common.ChannelSocket init > INFO: JK: ajp13 listening on /0.0.0.0:8009 > Jan 4, 2008 3:36:50 PM org.apache.jk.server.JkMain start > INFO: Jk running ID=0 time=0/52 config=null > Jan 4, 2008 3:36:50 PM org.apache.catalina.startup.Catalina start > INFO: Server startup in 5161 ms > > > Any idea? > Michele > > > On 4 Jan 2008, at 14:50, robert lazarski wrote: > > > Michele, can you post your entire stacktrace please? I can't match the > > error you get with current svn. The error you are getting indicates no > > soapmonitorPhase in inflow, yet your axis2.xml does have it. So > > sorry, no clear indication of the problem yet. You could try putting > > axis2 in debug to see the phases loaded, which may flush out the error > > by confirming the phase isn't loaded. > > > > Alternatively, try out tcpmon ;-) . > > > > Good luck, > > Robert > > > > On Jan 4, 2008 10:11 AM, Michele Mazzucco > > <[EMAIL PROTECTED]> wrote: > >> Robert, > >> > >> if the module is globally engaged I get the error I mentioned in my > >> previous email. The same happens also if I "dynamically" engage the > >> module. > >> > >> Michele > >> > >> > >> On 4 Jan 2008, at 12:01, robert lazarski wrote: > >> > >>> You need to engage the module. Search for: > >>> > >>> > >>> > >>> Then in the same place, add: > >>> > >>> > >>> > >>> HTH, > >>> Robert > >>> > >>> On Jan 4, 2008 8:44 AM, Michele Mazzucco > >>> <[EMAIL PROTECTED]> wrote: > >>>> Robert, > >>>> > >>>> in axis2 1.3 all the phases needed by the soap monitor module are > >>>> already included. > >>>> > >>>> > >>>> > >>>> > >>>> Michele > >>>> > >>>> On 4 Jan 2008, at 11:07, robert lazarski wrote: > >>>> > >>>>> The exception is pretty self descriptive... show us the entire > >>>>> axis2.xml and maybe we can help. > >>>>> > >>>>> Robert > >>>>> > >>>>> On Jan 4, 2008 7:39 AM, Michele Mazzucco > >>>>> <[EMAIL PROTECTED]> wrote: > >>>>>> Hi all, > >>>>>> > >>>>>> I can't enage the soapmonitor module under Axis2 1.
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Robert, I get that error if I run an embedded version of axis2. If I deploy it to tomcat (clean setup) it works fine. Jan 4, 2008 3:36:45 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Jan 4, 2008 3:36:45 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1011 ms Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Jan 4, 2008 3:36:46 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.14 Jan 4, 2008 3:36:46 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive axis2.war [INFO] Deploying module: addressing-1.3 [INFO] Deploying module: metadataExchange-1.3 [INFO] Deploying module: ping-1.3 [INFO] Deploying module: script-1.3 [INFO] Deploying module: soapmonitor-1.3 [INFO] script module activated [INFO] HTTP Sender starting [INFO] Deploying Web service: version.aar Jan 4, 2008 3:36:50 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Jan 4, 2008 3:36:50 PM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Jan 4, 2008 3:36:50 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/52 config=null Jan 4, 2008 3:36:50 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 5161 ms Any idea? Michele On 4 Jan 2008, at 14:50, robert lazarski wrote: Michele, can you post your entire stacktrace please? I can't match the error you get with current svn. The error you are getting indicates no soapmonitorPhase in inflow, yet your axis2.xml does have it. So sorry, no clear indication of the problem yet. You could try putting axis2 in debug to see the phases loaded, which may flush out the error by confirming the phase isn't loaded. Alternatively, try out tcpmon ;-) . Good luck, Robert On Jan 4, 2008 10:11 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, if the module is globally engaged I get the error I mentioned in my previous email. The same happens also if I "dynamically" engage the module. Michele On 4 Jan 2008, at 12:01, robert lazarski wrote: You need to engage the module. Search for: Then in the same place, add: HTH, Robert On Jan 4, 2008 8:44 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, in axis2 1.3 all the phases needed by the soap monitor module are already included. Michele On 4 Jan 2008, at 11:07, robert lazarski wrote: The exception is pretty self descriptive... show us the entire axis2.xml and maybe we can help. Robert On Jan 4, 2008 7:39 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Hi all, I can't enage the soapmonitor module under Axis2 1.3 because of the following error org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 'soapmonitorPhase' while deploying handler 'InFlowSOAPMonitorHandler'. My axis2.xml differs from the default one only because of the NIO transport listener. Any idea? Thanks, Michele - -- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Michele, can you post your entire stacktrace please? I can't match the error you get with current svn. The error you are getting indicates no soapmonitorPhase in inflow, yet your axis2.xml does have it. So sorry, no clear indication of the problem yet. You could try putting axis2 in debug to see the phases loaded, which may flush out the error by confirming the phase isn't loaded. Alternatively, try out tcpmon ;-) . Good luck, Robert On Jan 4, 2008 10:11 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Robert, > > if the module is globally engaged I get the error I mentioned in my > previous email. The same happens also if I "dynamically" engage the > module. > > Michele > > > On 4 Jan 2008, at 12:01, robert lazarski wrote: > > > You need to engage the module. Search for: > > > > > > > > Then in the same place, add: > > > > > > > > HTH, > > Robert > > > > On Jan 4, 2008 8:44 AM, Michele Mazzucco > > <[EMAIL PROTECTED]> wrote: > >> Robert, > >> > >> in axis2 1.3 all the phases needed by the soap monitor module are > >> already included. > >> > >> > >> > >> > >> Michele > >> > >> On 4 Jan 2008, at 11:07, robert lazarski wrote: > >> > >>> The exception is pretty self descriptive... show us the entire > >>> axis2.xml and maybe we can help. > >>> > >>> Robert > >>> > >>> On Jan 4, 2008 7:39 AM, Michele Mazzucco > >>> <[EMAIL PROTECTED]> wrote: > >>>> Hi all, > >>>> > >>>> I can't enage the soapmonitor module under Axis2 1.3 because of the > >>>> following error > >>>> org.apache.axis2.phaseresolver.PhaseException: Did not find the > >>>> desired phase 'soapmonitorPhase' while deploying handler > >>>> 'InFlowSOAPMonitorHandler'. > >>>> > >>>> My axis2.xml differs from the default one only because of the NIO > >>>> transport listener. > >>>> > >>>> > >>>> Any idea? > >>>> > >>>> Thanks, > >>>> Michele > >>>> > >>>> > >>>> --- > >>>> -- > >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>> For additional commands, e-mail: [EMAIL PROTECTED] > >>>> > >>>> > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >> > >> > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Robert, if the module is globally engaged I get the error I mentioned in my previous email. The same happens also if I "dynamically" engage the module. Michele On 4 Jan 2008, at 12:01, robert lazarski wrote: You need to engage the module. Search for: Then in the same place, add: HTH, Robert On Jan 4, 2008 8:44 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Robert, in axis2 1.3 all the phases needed by the soap monitor module are already included. Michele On 4 Jan 2008, at 11:07, robert lazarski wrote: The exception is pretty self descriptive... show us the entire axis2.xml and maybe we can help. Robert On Jan 4, 2008 7:39 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Hi all, I can't enage the soapmonitor module under Axis2 1.3 because of the following error org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 'soapmonitorPhase' while deploying handler 'InFlowSOAPMonitorHandler'. My axis2.xml differs from the default one only because of the NIO transport listener. Any idea? Thanks, Michele --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
You need to engage the module. Search for: Then in the same place, add: HTH, Robert On Jan 4, 2008 8:44 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Robert, > > in axis2 1.3 all the phases needed by the soap monitor module are > already included. > > > > > Michele > > On 4 Jan 2008, at 11:07, robert lazarski wrote: > > > The exception is pretty self descriptive... show us the entire > > axis2.xml and maybe we can help. > > > > Robert > > > > On Jan 4, 2008 7:39 AM, Michele Mazzucco > > <[EMAIL PROTECTED]> wrote: > >> Hi all, > >> > >> I can't enage the soapmonitor module under Axis2 1.3 because of the > >> following error > >> org.apache.axis2.phaseresolver.PhaseException: Did not find the > >> desired phase 'soapmonitorPhase' while deploying handler > >> 'InFlowSOAPMonitorHandler'. > >> > >> My axis2.xml differs from the default one only because of the NIO > >> transport listener. > >> > >> > >> Any idea? > >> > >> Thanks, > >> Michele > >> > >> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Robert, in axis2 1.3 all the phases needed by the soap monitor module are already included. axis2-xml.tar.gz Description: GNU Zip compressed data Michele On 4 Jan 2008, at 11:07, robert lazarski wrote: The exception is pretty self descriptive... show us the entire axis2.xml and maybe we can help. Robert On Jan 4, 2008 7:39 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Hi all, I can't enage the soapmonitor module under Axis2 1.3 because of the following error org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 'soapmonitorPhase' while deploying handler 'InFlowSOAPMonitorHandler'. My axis2.xml differs from the default one only because of the NIO transport listener. Any idea? Thanks, Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
Hi Michele, You have to add the soapmonitorPhase ( at the moment ) to the axis2.xml to use soap monitor module. You can find the details here [1]. Thanks, Nandana [1] - http://ws.apache.org/axis2/1_3/soapmonitor-module.html On Jan 4, 2008 3:09 PM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Hi all, > > I can't enage the soapmonitor module under Axis2 1.3 because of the > following error > org.apache.axis2.phaseresolver.PhaseException: Did not find the > desired phase 'soapmonitorPhase' while deploying handler > 'InFlowSOAPMonitorHandler'. > > My axis2.xml differs from the default one only because of the NIO > transport listener. > > > Any idea? > > Thanks, > Michele > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: [Axis2] Unable to engage the soap monitor module (axis2 1.3)
The exception is pretty self descriptive... show us the entire axis2.xml and maybe we can help. Robert On Jan 4, 2008 7:39 AM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > Hi all, > > I can't enage the soapmonitor module under Axis2 1.3 because of the > following error > org.apache.axis2.phaseresolver.PhaseException: Did not find the > desired phase 'soapmonitorPhase' while deploying handler > 'InFlowSOAPMonitorHandler'. > > My axis2.xml differs from the default one only because of the NIO > transport listener. > > > Any idea? > > Thanks, > Michele > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Unable to engage the soap monitor module (axis2 1.3)
Hi all, I can't enage the soapmonitor module under Axis2 1.3 because of the following error org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 'soapmonitorPhase' while deploying handler 'InFlowSOAPMonitorHandler'. My axis2.xml differs from the default one only because of the NIO transport listener. Any idea? Thanks, Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SOAP Monitor
http://ws.apache.org/commons/tcpmon/ or http://www.pocketsoap.com/tcptrace/ On 3/13/07, Rich Adili <[EMAIL PROTECTED]> wrote: Hi, I'm using Axis2, v1.1.1, client-side only. Talking to a .NET server. Looks like I can't use soapmonitor in this configuration. Any clever ideas? Thx, Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SOAP Monitor
You can't use soapmonitor just on the client side, but you can use tcpmon. HTH, Robert On 3/13/07, Rich Adili <[EMAIL PROTECTED]> wrote: Hi, I'm using Axis2, v1.1.1, client-side only. Talking to a .NET server. Looks like I can't use soapmonitor in this configuration. Any clever ideas? Thx, Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SOAP Monitor
Hi, I'm using Axis2, v1.1.1, client-side only. Talking to a .NET server. Looks like I can't use soapmonitor in this configuration. Any clever ideas? Thx, Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
In SOAP Monitor unable to see web service request/response messages
Hi, I have enabled the SOAP Monitor as specified in the Axis Installation document. When I re-deploy the SOAP Monitor web service, I am able to see request & response messages. I am running a web service from Tomcat using spring framework and working-mouse spring axis servlet. I am able to invoke this web service from a simple axis client program, but could not see the request/response messages in SOAP Monitor. Am I facing this problem because of working-mouse spring axis servlet? Here I am attaching the server-config.wsdd of my web service. Any help or suggestions are highly appreciated. Thanks Sudhakar http://www.nabble.com/file/5580/server-config.wsdd server-config.wsdd -- View this message in context: http://www.nabble.com/In-SOAP-Monitor-unable-to-see-web-service-request-response-messages-tf2958046.html#a8275121 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SOAP Monitor
The docs now say:
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/latest/soapmonitor-module.html
Alternatively, you can get the compiled applet classes from the
axis2-soapmonitor-*.jar from inside the expanded axis2.war under
WEB-INF/lib .
If anyone has suggestions on how to improve the wording just post them
to the list, or reply to this thread ;-) .
HTH,
Robert
On 9/6/06, Nirmit Desai <[EMAIL PROTECTED]> wrote:
axis2-soapmonitor.jar is inside WEB-INF/lib of axis2.war in Axis2 1.0
distro.
If you are using nightlies, you should have axis2-soapmonitor-SNAPSHOT.jar
instead at the same location.
I just extracted out SOAPMonitor*.class from this jar into my webapps/axis2
and it works great. I found that part of the documentation confusing too,
no compilation was necessary.
-Nirmit
"Doolittle, Todd"
<[EMAIL PROTECTED]
.com> To
09/06/2006 01:32 cc
PM
Subject
SOAP Monitor
Please respond to
[EMAIL PROTECTED]
he.org
I followed the documentation for using the SOAP monitor. However it says
to compile the applet with "javac -classpath axis2-soapmonitor.jar
SOAPMonitorApplet.java" Neither axis2-soamonitor.jar nor
SOAPMonitorApplet.java are part of the Axis2 distribution. And unless I'm
missing it, I don't see where I can download them off the Axis2 website.
Can anyone tell me where to get them?
Thanks!
Todd
This message, including any attachments, is the property of Sears Holdings
Corporation and/or one of its subsidiaries. It is confidential and may
contain proprietary or legally privileged information. If you are not the
intended recipient, please delete it without reading the contents. Thank
you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: SOAP Monitor
axis2-soapmonitor.jar is inside WEB-INF/lib of axis2.war in Axis2 1.0
distro.
If you are using nightlies, you should have axis2-soapmonitor-SNAPSHOT.jar
instead at the same location.
I just extracted out SOAPMonitor*.class from this jar into my webapps/axis2
and it works great. I found that part of the documentation confusing too,
no compilation was necessary.
-Nirmit
"Doolittle, Todd"
<[EMAIL PROTECTED]
.com> To
09/06/2006 01:32 cc
PM
Subject
SOAP Monitor
Please respond to
[EMAIL PROTECTED]
he.org
I followed the documentation for using the SOAP monitor. However it says
to compile the applet with “javac -classpath axis2-soapmonitor.jar
SOAPMonitorApplet.java” Neither axis2-soamonitor.jar nor
SOAPMonitorApplet.java are part of the Axis2 distribution. And unless I’m
missing it, I don’t see where I can download them off the Axis2 website.
Can anyone tell me where to get them?
Thanks!
Todd
This message, including any attachments, is the property of Sears Holdings
Corporation and/or one of its subsidiaries. It is confidential and may
contain proprietary or legally privileged information. If you are not the
intended recipient, please delete it without reading the contents. Thank
you.
Re: SOAP Monitor
Hi Todd, couple of things: The jar is inside the WAR under /WEB-INF/lib . I'll change the docs to reflect that ... since it relates to the applet , there's not much use of the jar outside the WAR . The applet source file is part of the src distro ... but in the latest docs under svn there has been changes that explain you can get the applet classes in compiled form from the jar: http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/latest/soapmonitor-module.html "Alternatively, you can get the compiled applet classes from the axis2-soapmonitor-*.jar ." Word to the wise ... the 1.0 release has a number of problems so I recommend the nightlies: http://people.apache.org/dist/axis2/nightly/ So deploy the war, and get the axis2-soapmonitor-*.jar from under WEB-INF/lib . HTH, Robert On 9/6/06, Doolittle, Todd <[EMAIL PROTECTED]> wrote: I followed the documentation for using the SOAP monitor. However it says to compile the applet with "javac -classpath axis2-soapmonitor.jar SOAPMonitorApplet.java" Neither axis2-soamonitor.jar nor SOAPMonitorApplet.java are part of the Axis2 distribution. And unless I'm missing it, I don't see where I can download them off the Axis2 website. Can anyone tell me where to get them? Thanks! Todd This message, including any attachments, is the property of Sears Holdings Corporation and/or one of its subsidiaries. It is confidential and may contain proprietary or legally privileged information. If you are not the intended recipient, please delete it without reading the contents. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: SOAP Monitor
Title: SOAP Monitor Hi Todd, I used the SOAPMonitorApplet.java from axis 1.4 download, compiled it and it is working fine for me. Syam From: Doolittle, Todd [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 06, 2006 12:32 PM To: axis-user@ws.apache.org Subject: SOAP Monitor I followed the documentation for using the SOAP monitor. However it says to compile the applet with “javac -classpath axis2-soapmonitor.jar SOAPMonitorApplet.java” Neither axis2-soamonitor.jar nor SOAPMonitorApplet.java are part of the Axis2 distribution. And unless I’m missing it, I don’t see where I can download them off the Axis2 website. Can anyone tell me where to get them? Thanks! Todd This message, including any attachments, is the property of Sears Holdings Corporation and/or one of its subsidiaries. It is confidential and may contain proprietary or legally privileged information. If you are not the intended recipient, please delete it without reading the contents. Thank you.
SOAP Monitor
Title: SOAP Monitor I followed the documentation for using the SOAP monitor. However it says to compile the applet with “javac -classpath axis2-soapmonitor.jar SOAPMonitorApplet.java” Neither axis2-soamonitor.jar nor SOAPMonitorApplet.java are part of the Axis2 distribution. And unless I’m missing it, I don’t see where I can download them off the Axis2 website. Can anyone tell me where to get them? Thanks! Todd This message, including any attachments, is the property of Sears Holdings Corporation and/or one of its subsidiaries. It is confidential and may contain proprietary or legally privileged information. If you are not the intended recipient, please delete it without reading the contents. Thank you.
Re: [Axis 2][1.0] Enabling the SOAP Monitor
Hi James! The axis part of the SOAPMonitor does not show up in the service list of axis2 because it is implemented as module and not as a service. In axis1 a service was used. Fabian James Loghry wrote, On 24.05.2006 16:13: One final problem I am having though, is I can access SOAPMonitor via http://localhost:8080/axis2/SOAPMonitor, but it does not show up on the axis2 services like it did for axis 1.x. However, this issue is insignificant. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis 2][1.0] Enabling the SOAP Monitor
I finally got it to work. The problem I was having was this: I was
copying and pasting the entire section and overriding
the section of my axis2.xml file. In order to correct this problem, I
just copied and pasted the elements which referenced "soapmonitorPhase"
into their respective places in the axis2.xml file.
One final problem I am having though, is I can access SOAPMonitor via
http://localhost:8080/axis2/SOAPMonitor, but it does not show up on the
axis2 services like it did for axis 1.x. However, this issue is
insignificant.
Thank you for all your help.
Kinichiro Inoguchi wrote:
> You could see this message in your logs;
> 2006-05-24 08:25:23 StandardContext[/axis2]Servlet /axis2 threw load()
> exception
> javax.servlet.ServletException: Invalid phases please recheck axis2.xml
> {0} for the handler {1}
>
> How did you modify your axis2.xml ?
>
> You should check,
> (tomcat)/webapps/axis2/WEB-INF/conf/axis2.xml
> (tomcat)/webapps/axis2/WEB-INF/web.xml
>
> Regards,
> kinichiro
>
> __
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
James Loghry
Software Engineer
The Krell Institute
1609 Golden Aspen Dr., Suite 101
Ames, IA 50010
http://www.krellinst.org
Phone: (515) 956 - 3696
Email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis 2][1.0] Enabling the SOAP Monitor
You could see this message in your logs;
2006-05-24 08:25:23 StandardContext[/axis2]Servlet /axis2 threw load()
exception
javax.servlet.ServletException: Invalid phases please recheck axis2.xml
{0} for the handler {1}
How did you modify your axis2.xml ?
You should check,
(tomcat)/webapps/axis2/WEB-INF/conf/axis2.xml
(tomcat)/webapps/axis2/WEB-INF/web.xml
Regards,
kinichiro
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis 2][1.0] Enabling the SOAP Monitor
It's a bit lengthy, but here's the stack trace I get after I redeploy axis2 on Tomcat and try to access the axis2 service... Any ideas? Thanks again, - James 2006-05-24 08:25:15 StandardContext[/manager]HTMLManager: list: Listing contexts for virtual host 'localhost' 2006-05-24 08:25:18 ApplicationDispatcher[/axis2] Servlet.service() for servlet jsp threw exception java.lang.NullPointerException at org.apache.jsp.axis2_002dweb.include.httpbase_jsp.jspInit(httpbase_jsp.java:22) at org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:75) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:144) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:307) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) at org.apache.jsp.axis2_002dweb.index_jsp._jspService(index_jsp.java:73) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Unknown Source) 2006-05-24 08:25:18 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception java.lang.NullPointerException at org.apache.jsp.axis2_002dweb.include.httpbase_jsp.jspInit(httpbase_jsp.java:22) at org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:75) at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:144) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:307) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.Appl
Re: [Axis 2][1.0] Enabling the SOAP Monitor
Step 3 is fine. Robert http://www.braziloutsource.com/On 5/23/06, Kinichiro Inoguchi <[EMAIL PROTECTED] > wrote:James,I could see SOAPMonitor with Axis2 1.0.1. modify axis2.xml as mentioned in instructions.2. modify web.xml as mentioned in instructions.3. extract SOAPMonitorApplet*.class files from axis2-soapmonitor-1.0.jar to (tomcat)/webapps/axis2/.I could see SOAPMonitor via http://localhost:8080/axis2/SOAPMonitorI don't know whether 3. is right way or not, though.Regards,kinichiro--- robert lazarski < [EMAIL PROTECTED]> wrote:> The compiled applet classes go in axis2/*applet*.class/WEB-INF/ .> Show a> stacktrace and maybe we can help.>> Robert> http://www.braziloutsource.com/>> On 5/23/06, James Loghry <[EMAIL PROTECTED]> wrote:> >> > How does one go about enabling the SOAP Monitor in Apache 2.0?> > I've tried following the instructions, but when I redeploy Axis2 in> > Tomcat, I get a NullPointerException.> >> > Where do the .class files go? Am I missing anything else possibly? > >> > Thanks,> > - James> >> >> -> > To unsubscribe, e-mail: [EMAIL PROTECTED]> > For additional commands, e-mail: [EMAIL PROTECTED]> >> >>__ Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection aroundhttp://mail.yahoo.com- To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis 2][1.0] Enabling the SOAP Monitor
James, I could see SOAPMonitor with Axis2 1.0. 1. modify axis2.xml as mentioned in instructions. 2. modify web.xml as mentioned in instructions. 3. extract SOAPMonitorApplet*.class files from axis2-soapmonitor-1.0.jar to (tomcat)/webapps/axis2/. I could see SOAPMonitor via http://localhost:8080/axis2/SOAPMonitor I don't know whether 3. is right way or not, though. Regards, kinichiro --- robert lazarski <[EMAIL PROTECTED]> wrote: > The compiled applet classes go in axis2/*applet*.class/WEB-INF/ . > Show a > stacktrace and maybe we can help. > > Robert > http://www.braziloutsource.com/ > > On 5/23/06, James Loghry <[EMAIL PROTECTED]> wrote: > > > > How does one go about enabling the SOAP Monitor in Apache 2.0? > > I've tried following the instructions, but when I redeploy Axis2 in > > Tomcat, I get a NullPointerException. > > > > Where do the .class files go? Am I missing anything else possibly? > > > > Thanks, > > - James > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis 2][1.0] Enabling the SOAP Monitor
The compiled applet classes go in axis2/*applet*.class/WEB-INF/ . Show a stacktrace and maybe we can help. Robert http://www.braziloutsource.com/On 5/23/06, James Loghry <[EMAIL PROTECTED] > wrote:How does one go about enabling the SOAP Monitor in Apache 2.0?I've tried following the instructions, but when I redeploy Axis2 in Tomcat, I get a NullPointerException.Where do the .class files go? Am I missing anything else possibly?Thanks,- James- To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
[Axis 2][1.0] Enabling the SOAP Monitor
How does one go about enabling the SOAP Monitor in Apache 2.0? I've tried following the instructions, but when I redeploy Axis2 in Tomcat, I get a NullPointerException. Where do the .class files go? Am I missing anything else possibly? Thanks, - James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Enable soap monitor
See me responses inline. On 5/10/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: Hi, Not able to understand this point 3) Deploy the soapmonitor web service via the admin client The soap monitor in axis 1.x also has a wsdd - which IIRC needs to be deployed first. And "assuming a axis.war" This requires axis to be deployed along with my web application ? Nope - you can use myApp.war just fine. Is this url http://localhost:8080/axis/services/AdminService to be converted to http://localhost:8080/mywebcontext/myservices/myservice ? Yes. HTH, Robert http://www.braziloutsource.com/ Sorry. Haven't worked with axis before ? Thanks, Mohan From: robert lazarski [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 09, 2006 5:54 PM To: axis-user@ws.apache.org Subject: Re: Enable soap monitor The steps in axis 1.x, assuming a axis.war, are: 1) Compile the applet and put it under axis/*applet.class*/WEB-INF 2) Configure the soapmonitor servlet via web.xml 3) Deploy the soapmonitor web service via the admin client 4) Place references in your web service wsdd such as: 5) Load the soap applet in a java 1.3 and higher enabled browser via: http://localhost:8080/axis/SOAPMonitor HTH, Robert http://www.braziloutsource.com/ On 5/9/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: Hi, I am trying to enable the soap monitor for my liferay portal application. The first step is to install axis along with this web application. Is that correct ? What does the url in the following axis instruction mean ? I have to substitute "axis" with my web application context ?? What does this "services/AdminService" mean ? What do I substitute it with ? "Deploy the SOAPMonitorService web service with the admin client and the deploy-monitor.wsdd file " java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient -lhttp://localhost:8080/axis/services/AdminService deploy-monitor.wsdd I am trying to monitor my WSRP communication. Thanks, Mohan This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
RE: Enable soap monitor
Hi, Not able to understand this point 3) Deploy the soapmonitor web service via the admin client And “assuming a axis.war” This requires axis to be deployed along with my web application ? Is this url http://localhost:8080/axis/services/AdminService to be converted to http://localhost:8080/mywebcontext/myservices/myservice ? Sorry. Haven’t worked with axis before ? Thanks, Mohan From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 5:54 PM To: axis-user@ws.apache.org Subject: Re: Enable soap monitor The steps in axis 1.x, assuming a axis.war, are: 1) Compile the applet and put it under axis/*applet.class*/WEB-INF 2) Configure the soapmonitor servlet via web.xml 3) Deploy the soapmonitor web service via the admin client 4) Place references in your web service wsdd such as: 5) Load the soap applet in a java 1.3 and higher enabled browser via: http://localhost:8080/axis/SOAPMonitor HTH, Robert http://www.braziloutsource.com/ On 5/9/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: Hi, I am trying to enable the soap monitor for my liferay portal application. The first step is to install axis along with this web application. Is that correct ? What does the url in the following axis instruction mean ? I have to substitute "axis" with my web application context ?? What does this "services/AdminService" mean ? What do I substitute it with ? "Deploy the SOAPMonitorService web service with the admin client and the deploy-monitor.wsdd file " java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient -lhttp://localhost:8080/axis/services/AdminService deploy-monitor.wsdd I am trying to monitor my WSRP communication. Thanks, Mohan This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: Enable soap monitor
The steps in axis 1.x, assuming a axis.war, are: 1) Compile the applet and put it under axis/*applet.class*/WEB-INF 2) Configure the soapmonitor servlet via web.xml 3) Deploy the soapmonitor web service via the admin client 4) Place references in your web service wsdd such as: 5) Load the soap applet in a java 1.3 and higher enabled browser via: http://localhost:8080/axis/SOAPMonitor HTH, Roberthttp://www.braziloutsource.com/ On 5/9/06, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: Hi, I am trying to enable the soap monitor for my liferay portal application. The first step is to install axis along with this web application. Is that correct ? What does the url in the following axis instruction mean ? I have to substitute "axis" with my web application context ?? What does this "services/AdminService" mean ? What do I substitute it with ? "Deploy the SOAPMonitorService web service with the admin client and the deploy-monitor.wsdd file " java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient -lhttp://localhost:8080/axis/services/AdminService deploy-monitor.wsdd I am trying to monitor my WSRP communication. Thanks, Mohan This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Enable soap monitor
Hi, I am trying to enable the soap monitor for my liferay portal application. The first step is to install axis along with this web application. Is that correct ? What does the url in the following axis instruction mean ? I have to substitute "axis" with my web application context ?? What does this "services/AdminService" mean ? What do I substitute it with ? "Deploy the SOAPMonitorService web service with the admin client and the deploy-monitor.wsdd file " java -cp %AXISCLASSPATH% org.apache.axis.client.AdminClient -lhttp://localhost:8080/axis/services/AdminService deploy-monitor.wsdd I am trying to monitor my WSRP communication. Thanks, Mohan This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
Re: [Axis2] 0.95 SOAP Monitor?
I'm back from vacation, will apply patch soon. Robert http://www.braziloutsource.com/On 4/8/06, Davanum Srinivas <[EMAIL PROTECTED] > wrote:Guys,porting has already been done someone has to apply the patch and test... http://issues.apache.org/jira/browse/AXIS2-434-- dimsOn 4/8/06, Ajith Ranabahu <[EMAIL PROTECTED] > wrote:> Hi,> I'm thinking that what you want is something like the SOAPMonitor -> unfortunatley which we have not built yet. However you can easily> write a pair of handlers that can be bundled into a module and act as > a logger for Axis2:)>> On 4/8/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:> > Hi Sebastian,> >> > What is your exact requirement ? Do you wanna just see the messages or > > you wanna log the messages ?> >> > If you wanna just see the messages, route your messages through TCPMon> > ( http://svn.apache.org/repos/asf/webservices/commons/trunk/modules/tcpmon/).> >> > If you wanna log the messages, write a logging handler, put that to all> > the flows using the module.xml , create a module, and deploy that in> > Axis2 war.> >> > HTH.> >> > Chinthaka> >> > Sebastian J. Schultheiss wrote:> > > Hello,> > > > > > is there a way to monitor the SOAP messages using the Axis2 WAR distribution> > > inside Tomcat? Can we just install a service that does this? There seems to be> > > some software in Axis 1.x, but we didn't find anything on the documentation> > > pages of Axis2.> > >> > > Thanks for your help,> > >> > > -- Sebi> > >> > > >> >> >> --> Ajith Ranabahu>--Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2] 0.95 SOAP Monitor?
Guys, porting has already been done someone has to apply the patch and test... http://issues.apache.org/jira/browse/AXIS2-434 -- dims On 4/8/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > Hi, > I'm thinking that what you want is something like the SOAPMonitor - > unfortunatley which we have not built yet. However you can easily > write a pair of handlers that can be bundled into a module and act as > a logger for Axis2:) > > On 4/8/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > > Hi Sebastian, > > > > What is your exact requirement ? Do you wanna just see the messages or > > you wanna log the messages ? > > > > If you wanna just see the messages, route your messages through TCPMon > > (http://svn.apache.org/repos/asf/webservices/commons/trunk/modules/tcpmon/). > > > > If you wanna log the messages, write a logging handler, put that to all > > the flows using the module.xml, create a module, and deploy that in > > Axis2 war. > > > > HTH. > > > > Chinthaka > > > > Sebastian J. Schultheiss wrote: > > > Hello, > > > > > > is there a way to monitor the SOAP messages using the Axis2 WAR > > > distribution > > > inside Tomcat? Can we just install a service that does this? There seems > > > to be > > > some software in Axis 1.x, but we didn't find anything on the > > > documentation > > > pages of Axis2. > > > > > > Thanks for your help, > > > > > > -- Sebi > > > > > > > > > > > > > > > > -- > Ajith Ranabahu > -- Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2] 0.95 SOAP Monitor?
Hi, I'm thinking that what you want is something like the SOAPMonitor - unfortunatley which we have not built yet. However you can easily write a pair of handlers that can be bundled into a module and act as a logger for Axis2:) On 4/8/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > Hi Sebastian, > > What is your exact requirement ? Do you wanna just see the messages or > you wanna log the messages ? > > If you wanna just see the messages, route your messages through TCPMon > (http://svn.apache.org/repos/asf/webservices/commons/trunk/modules/tcpmon/). > > If you wanna log the messages, write a logging handler, put that to all > the flows using the module.xml, create a module, and deploy that in > Axis2 war. > > HTH. > > Chinthaka > > Sebastian J. Schultheiss wrote: > > Hello, > > > > is there a way to monitor the SOAP messages using the Axis2 WAR distribution > > inside Tomcat? Can we just install a service that does this? There seems to > > be > > some software in Axis 1.x, but we didn't find anything on the documentation > > pages of Axis2. > > > > Thanks for your help, > > > > -- Sebi > > > > > > > -- Ajith Ranabahu
Re: [Axis2] 0.95 SOAP Monitor?
Hi Sebastian, What is your exact requirement ? Do you wanna just see the messages or you wanna log the messages ? If you wanna just see the messages, route your messages through TCPMon (http://svn.apache.org/repos/asf/webservices/commons/trunk/modules/tcpmon/). If you wanna log the messages, write a logging handler, put that to all the flows using the module.xml, create a module, and deploy that in Axis2 war. HTH. Chinthaka Sebastian J. Schultheiss wrote: > Hello, > > is there a way to monitor the SOAP messages using the Axis2 WAR distribution > inside Tomcat? Can we just install a service that does this? There seems to be > some software in Axis 1.x, but we didn't find anything on the documentation > pages of Axis2. > > Thanks for your help, > > -- Sebi > signature.asc Description: OpenPGP digital signature
[Axis2] 0.95 SOAP Monitor?
Hello, is there a way to monitor the SOAP messages using the Axis2 WAR distribution inside Tomcat? Can we just install a service that does this? There seems to be some software in Axis 1.x, but we didn't find anything on the documentation pages of Axis2. Thanks for your help, -- Sebi
SOAP Monitor unable to communicate with server
Hi, I was trying to set up the SOAP monitor for axis v1.2. I followed the user guide, up to the point where the SOAPMonitor Applet shows up at http://localhost:8080/axis/SOAPMonitor. However at the bottom it says 'the SOAP Monitor is unable to communicate with the server'. I dug through the mailing list achieve. This issue has been raised a couple times without a direct answer. Would somebody be kind enough to shed some lights onto this? Sincerely Hanxi
Again, about SOAP monitor service in Axis 1.2
Title: Message Hi guys, another question about SOAP monitor! I deployed a service called "EchoService" which sends a SOAP message to call the sample service "MyService" included in Axis 1.2 package to echo a string. Client <> "EchoService" <> "MyService" I register "EchoService" in the SOAP monitor service to monitor the SOAP messages go in and out of the service. But the SOAP monitor only captures the request message sent from the client to "EchoService" and response message sent from "EchoService" to the client. The SOAP message sent from "EchoService" to "MyService" is not captured. Is there a way to make the SOAP monitor to capture the SOAP request message sent from "EchoService" to "MyService"?? looking forward to your reply Zheng
RE: [SPAM_EMAIL] - A simple question about SOAP monitor in Axis 1.2 - Email has different SMTP TO: and MIME TO: fields in the email addresses
Hi, SOAP Monitor Service is a handler which can be integrated with both client as well as server side handler chain of Axis Framework. So if you have installed this handler in your handler chain, all the message will be logged. Simply install this handler using client-config.wsdd in the client side path of S1 Web service. or using server-config.wsdd in the server side path of S2 web service. Thanks, Mohit. -Original Message- From: Zheng Li [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 17, 2005 2:43 PM To: axis-user@ws.apache.org Subject: [SPAM_EMAIL] - A simple question about SOAP monitor in Axis 1.2 - Email has different SMTP TO: and MIME TO: fields in the email addresses Hi guys: As we know, the SOAPMonitorService in Aixs 1.2 can monitor the request SOAP messages a Web service receives from the client, and resopnse messages a Web service sends to the client. But can it monitor the request SOAP messages a Web service sends to another Web service?? For example, Web service S1 sends a SOAP request message M1 to Web service S2 to invoke its method, can SOAPMonitorService monitor this SOAP request message M1?? Hope I make myself understood. Looking forward to your reply. Many thnx. Zheng
A simple question about SOAP monitor in Axis 1.2
Hi guys: As we know, the SOAPMonitorService in Aixs 1.2 can monitor the request SOAP messages a Web service receives from the client, and resopnse messages a Web service sends to the client. But can it monitor the request SOAP messages a Web service sends to another Web service?? For example, Web service S1 sends a SOAP request message M1 to Web service S2 to invoke its method, can SOAPMonitorService monitor this SOAP request message M1?? Hope I make myself understood. Looking forward to your reply. Many thnx. Zheng
Re: Is SOAP monitor tool available in AXIS2
Hi, We don't have the SOAP monitor tool/applet in axis2 but you can simply use tcpmon that you get with Axis1.x Axis 1.2 does not support WSDL 2.0 Thanks, Ruchith On 8/16/05, Zheng Li <[EMAIL PROTECTED]> wrote: > Hi guys: > > Just wanna knonw is the SOAP monitor tool included in Axis 1.2 also > available in Axis2?? I browse the doc of Axis2 but find no info about SOAP > monitor. > > BTW, does Axis 1.2 support WSDL 2.0?? > > Pls help. Thnx a lot! > > Zheng > > -- Ruchith
Re: Is SOAP monitor tool available in AXIS2
Hi Zheng; 0.91 release does not have SOAP monitor in built , I think it is nice to have that feature. If you can please create a JIRA issue then next release will be having SOAP monitor. does Axis 1.2 support WSDL 2.0 : nope Axis 1.2 does not support WSDL 2.0 but Axis2 does :) Thanks, Deepal ~Future is Open~ - Original Message - From: "Zheng Li" <[EMAIL PROTECTED]> To: Sent: Tuesday, August 16, 2005 2:09 PM Subject: Is SOAP monitor tool available in AXIS2 Hi guys: Just wanna knonw is the SOAP monitor tool included in Axis 1.2 also available in Axis2?? I browse the doc of Axis2 but find no info about SOAP monitor. BTW, does Axis 1.2 support WSDL 2.0?? Pls help. Thnx a lot! Zheng
Is SOAP monitor tool available in AXIS2
Hi guys: Just wanna knonw is the SOAP monitor tool included in Axis 1.2 also available in Axis2?? I browse the doc of Axis2 but find no info about SOAP monitor. BTW, does Axis 1.2 support WSDL 2.0?? Pls help. Thnx a lot! Zheng
Not able to see SOAP faults in SOAP Monitor
I was having webservice with definitions in server_config.wsdd as follows I can see successful SOAP requests and Responses. But do not see the failure response (SOAP Faults) What could be the problem ? http://schemas.cisco.com/ast/soap/"/> -Venky
axis soap monitor
hi I wanna use tcpmon, the soap monitor of axis but how can i now which port does my client use to connect with the webservice on localhost:8088 ? thanx for all _ Découvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vidéos ! Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com
SOAP Monitor not able to communicate with the server and how to undeploy the SOAP Monitor for redeployment
I've successfully got Axis 1.2rc2 going on my test workstation and decided to get everything set up on one of our content servers. What i did was install Java 1.4.2_08 on the content server and then proceded to scp my tomcat and axis install directories to the content servers. After adding in all the environment variables and paths, everything was good to go. Initial tests of the sample services were good, but when i went to start the SOAP Monitor, the applet loaded up fine, but it couldn't connect to the server. I tried changing the port variable in the source code from 0 to a port that we have open and redeploying the SOAP Monitor, but it didn't work. I'm not very versed in ports and things like that (as a matter of fact, I've just started using axis and java) and i'm wondering, what is the significance of this service and port 0? Why is the SOAP Monitor unable to connect to the server and which server is it trying to connect to? I thought maybe it was because you need to undeploy the service first before deploying it again, but i didn't find anything about undeploying the SOAP Monitor. I tried making my own undeploy.wsdd with the contents of: http://xml.apache.org/axis/wsdd/"; xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";> in order to undeploy the service, but after starting and restarting tomcat, the applet was still being loaded even though i hadn't redeployed the service yet. Any suggestions on helping me get the SOAP Monitor working would be greatly appreciated. If there's more information that you need, please let me know. Thanks for you consideration in this matter. Vincent J.
Re: Removing SOAP Monitor
Please don't feel like that. The whole purpose of this mailing list is to help each other out. I asked for more details so as to understand your problem. Sunil Kothari Valtech India DISCLAIMER: Any Information contained or transmitted in this e-mail and / or attachments may contain confidential data, proprietary to Majoris Systems Pvt Ltd., and / or the authors of the information and is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or email appears to have been sent to you by error, you are not authorised to access, read, disclose, copy, use or otherwise deal with it. If you have received this e-mail in error, please notify us immediately at mail to: [EMAIL PROTECTED] and delete this mail from your records. This is to notify that Majoris Systems Pvt Limited shall have no liability or obligation, legal or otherwise, for any errors, omissions, viruses or computer problems experienced as a result of this transmission since data over the public Internet cannot be guaranteed to be secure or error-free. - Original Message - From: Brian Abbott <[EMAIL PROTECTED]> Date: Tuesday, March 29, 2005 12:11 pm Subject: Re: Removing SOAP Monitor > I only commented at one location, the web.xml file. I > didnt find an entry in the wsdd file. Is there another > location. > > Actually... now that I read the exception... Sorry for > abusing the list. I should have checked this further > before coming to the list. Here's the 2nd level nested > exception: > > Mar 28, 2005 10:36:54 PM > org.apache.catalina.startup.ContextConfig > applicationConfig > SEVERE: Parse error in application web.xml > java.lang.IllegalArgumentException: Servlet mapping > specifies an unknown servlet name SOAPMonitorService >at > org.apache.commons.digester.Digester.createSAXException (Digester.java:2540) > > Now that I read it, it's totally odvious (further down > in the web.xml file). The primary exception was a call > to an apache-commons class. Anyway, I feel I abused > the list. Sorry about that. > > Brian > > > --- Sunil Kothari <[EMAIL PROTECTED]> wrote: > > Hi Brian > > I commented at two places and seems to > > work(SOAPMonitor is inaccessible > > now and other services deployed on the axis are > > working fine) for me. > > > > What is the exact message that you get and at what > > stage ? And also if > > you can give a detail on the configuration, that you > > are using, it > > would help in understanding your problems. > > > > Thanks, > > Sunil Kothari > > Valtech India > > > > DISCLAIMER: > > Any Information contained or transmitted in this > > e-mail and / or > > attachments may contain confidential data, > > proprietary to Majoris > > Systems Pvt Ltd., and / or the authors of the > > information and is > > intended for use only by the individual or entity to > > which it is > > addressed. If you are not the intended recipient or > > email appears > > to have been sent to you by error, you are not > > authorised to access, > > read, disclose, copy, use or otherwise deal with it. > > If you > > have received this e-mail in error, please notify us > > immediately at > > mail to: [EMAIL PROTECTED] and delete this mail > > from your records. > > > > This is to notify that Majoris Systems Pvt Limited > > shall have no > > liability or obligation, legal or otherwise, for any > > errors, > > omissions, viruses or computer problems experienced > > as a result of > > this transmission since data over the public > > Internet cannot be > > guaranteed to be secure or error-free. > > > > - Original Message - > > From: Brian Abbott <[EMAIL PROTECTED]> > > Date: Tuesday, March 29, 2005 11:30 am > > Subject: Removing SOAP Monitor > > > > > Hi, > > > > > > I am wondering if it is possible to remove > > > SOAPMonitorService from an AXIS deployment. I am > > > currently running AXIS from within Tomcat and, my > > goal > > > is to minimize the number of open ports that are > > > necesarry for a deployment. Ideally it would be > > only > > > one. > > > > > > I have currently removed the SOAPMonitorService > > > declaration from the web.xml file however, that > > seems > > > to break my deployed services. Any help would be > > > appreciated. > > > > > > Thanks, > > > > > > Brian > > > > > > > > > > > > __ > > > Do you Yahoo!? > > > Yahoo! Small Business - Try our new resources > > site! > > > http://smallbusiness.yahoo.com/resources/ > > > > > > > > > > > __ > Do you Yahoo!? > Yahoo! Small Business - Try our new resources site! > http://smallbusiness.yahoo.com/resources/ >
Re: Removing SOAP Monitor
I only commented at one location, the web.xml file. I didnt find an entry in the wsdd file. Is there another location. Actually... now that I read the exception... Sorry for abusing the list. I should have checked this further before coming to the list. Here's the 2nd level nested exception: Mar 28, 2005 10:36:54 PM org.apache.catalina.startup.ContextConfig applicationConfig SEVERE: Parse error in application web.xml java.lang.IllegalArgumentException: Servlet mapping specifies an unknown servlet name SOAPMonitorService at org.apache.commons.digester.Digester.createSAXException(Digester.java:2540) Now that I read it, it's totally odvious (further down in the web.xml file). The primary exception was a call to an apache-commons class. Anyway, I feel I abused the list. Sorry about that. Brian --- Sunil Kothari <[EMAIL PROTECTED]> wrote: > Hi Brian > I commented at two places and seems to > work(SOAPMonitor is inaccessible > now and other services deployed on the axis are > working fine) for me. > > What is the exact message that you get and at what > stage ? And also if > you can give a detail on the configuration, that you > are using, it > would help in understanding your problems. > > Thanks, > Sunil Kothari > Valtech India > > DISCLAIMER: > Any Information contained or transmitted in this > e-mail and / or > attachments may contain confidential data, > proprietary to Majoris > Systems Pvt Ltd., and / or the authors of the > information and is > intended for use only by the individual or entity to > which it is > addressed. If you are not the intended recipient or > email appears > to have been sent to you by error, you are not > authorised to access, > read, disclose, copy, use or otherwise deal with it. > If you > have received this e-mail in error, please notify us > immediately at > mail to: [EMAIL PROTECTED] and delete this mail > from your records. > > This is to notify that Majoris Systems Pvt Limited > shall have no > liability or obligation, legal or otherwise, for any > errors, > omissions, viruses or computer problems experienced > as a result of > this transmission since data over the public > Internet cannot be > guaranteed to be secure or error-free. > > - Original Message - > From: Brian Abbott <[EMAIL PROTECTED]> > Date: Tuesday, March 29, 2005 11:30 am > Subject: Removing SOAP Monitor > > > Hi, > > > > I am wondering if it is possible to remove > > SOAPMonitorService from an AXIS deployment. I am > > currently running AXIS from within Tomcat and, my > goal > > is to minimize the number of open ports that are > > necesarry for a deployment. Ideally it would be > only > > one. > > > > I have currently removed the SOAPMonitorService > > declaration from the web.xml file however, that > seems > > to break my deployed services. Any help would be > > appreciated. > > > > Thanks, > > > > Brian > > > > > > > > __ > > Do you Yahoo!? > > Yahoo! Small Business - Try our new resources > site! > > http://smallbusiness.yahoo.com/resources/ > > > > __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
Re: SOAP Monitor
Or - please use a console app version of SOAPMonitor, not the applet version. % java org.apache.axis.utils.SOAPMonitor <http://ws.apache.org/axis/java/soapmonitor-user-guide.html> Thanks, Toshi <[EMAIL PROTECTED]> On Tue, 29 Mar 2005, Sunil Kothari wrote: No, it's not possible with SOAPMonitor. Use TCPMon instead. There you can save and even modify and do resends. Sunil Kothari Valtech India - Original Message - From: "Jerome Gagner" <[EMAIL PROTECTED]> Date: Tuesday, March 29, 2005 5:51 am Subject: SOAP Monitor Hello, This is probably a stupid question, but is there a way I can copy-paiste the contents out of the SOAP Monitor Applet? - Jerome Gagner Director of Web Services [EMAIL PROTECTED]
Re: Removing SOAP Monitor
Hi Brian I commented at two places and seems to work(SOAPMonitor is inaccessible now and other services deployed on the axis are working fine) for me. What is the exact message that you get and at what stage ? And also if you can give a detail on the configuration, that you are using, it would help in understanding your problems. Thanks, Sunil Kothari Valtech India DISCLAIMER: Any Information contained or transmitted in this e-mail and / or attachments may contain confidential data, proprietary to Majoris Systems Pvt Ltd., and / or the authors of the information and is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or email appears to have been sent to you by error, you are not authorised to access, read, disclose, copy, use or otherwise deal with it. If you have received this e-mail in error, please notify us immediately at mail to: [EMAIL PROTECTED] and delete this mail from your records. This is to notify that Majoris Systems Pvt Limited shall have no liability or obligation, legal or otherwise, for any errors, omissions, viruses or computer problems experienced as a result of this transmission since data over the public Internet cannot be guaranteed to be secure or error-free. - Original Message - From: Brian Abbott <[EMAIL PROTECTED]> Date: Tuesday, March 29, 2005 11:30 am Subject: Removing SOAP Monitor > Hi, > > I am wondering if it is possible to remove > SOAPMonitorService from an AXIS deployment. I am > currently running AXIS from within Tomcat and, my goal > is to minimize the number of open ports that are > necesarry for a deployment. Ideally it would be only > one. > > I have currently removed the SOAPMonitorService > declaration from the web.xml file however, that seems > to break my deployed services. Any help would be > appreciated. > > Thanks, > > Brian > > > > __ > Do you Yahoo!? > Yahoo! Small Business - Try our new resources site! > http://smallbusiness.yahoo.com/resources/ >
Removing SOAP Monitor
Hi, I am wondering if it is possible to remove SOAPMonitorService from an AXIS deployment. I am currently running AXIS from within Tomcat and, my goal is to minimize the number of open ports that are necesarry for a deployment. Ideally it would be only one. I have currently removed the SOAPMonitorService declaration from the web.xml file however, that seems to break my deployed services. Any help would be appreciated. Thanks, Brian __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/
Re: SOAP Monitor
No, it's not possible with SOAPMonitor. Use TCPMon instead. There you can save and even modify and do resends. Sunil Kothari Valtech India DISCLAIMER: Any Information contained or transmitted in this e-mail and / or attachments may contain confidential data, proprietary to Majoris Systems Pvt Ltd., and / or the authors of the information and is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or email appears to have been sent to you by error, you are not authorised to access, read, disclose, copy, use or otherwise deal with it. If you have received this e-mail in error, please notify us immediately at mail to: [EMAIL PROTECTED] and delete this mail from your records. This is to notify that Majoris Systems Pvt Limited shall have no liability or obligation, legal or otherwise, for any errors, omissions, viruses or computer problems experienced as a result of this transmission since data over the public Internet cannot be guaranteed to be secure or error-free. - Original Message - From: "Jerome Gagner" <[EMAIL PROTECTED]> Date: Tuesday, March 29, 2005 5:51 am Subject: SOAP Monitor > Hello, > > This is probably a stupid question, but is there a way I can copy- > paiste the > contents out of the SOAP Monitor Applet? > > - > Jerome Gagner > Director of Web Services > [EMAIL PROTECTED] > >
SOAP Monitor
Hello, This is probably a stupid question, but is there a way I can copy-paiste the contents out of the SOAP Monitor Applet? - Jerome Gagner Director of Web Services [EMAIL PROTECTED]
