My advice is to move to axis2 if possible for many reasons including
performance and its more modern features. Looks like your applet isn't
even loading - you need at least java 1.3 in firefox / IE . If you get
the "load applet failed" error message, I'd check that java is
configured properly.

If all else fails, there is a tool called tcpmon that largely does the
same thing as the soap monitor as a stand alone, non-browser based
application.

HTH,
Robert

On Nov 28, 2007 2:38 AM, Wang Han <[EMAIL PROTECTED]> wrote:
> Hi Robert & Martin,
>
> Thanks for your reply.
>
> Robert:
> I also wonder this... I changed the web.xml and
> http://localhost:8080/axis/service/echo is changed to
> http://localhost:8080/echo.
> But originally the SOAPMonitor is deployed at
> http://localhost:8080/axis/SOAPMonitor (no 'services' in the url), so where
> should it be after I re-deployed the service? any suggestion is welcome :)
>
> Martin: do u mean we can use SOAPMonitor in axis2 independently? So if I
> have a service which is deployed at http://localhost:8080/echo, I can
> monitor it by
>
> http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=echo&submit=+Engage
> + regardless where the service is deployed?
> I have no idea about axis2 since I always work with axis1.4, is axis2 better
> than axis1.4 ?
>
> Thanks!
> Han
>
> On Nov 28, 2007 10:19 AM, robert lazarski < [EMAIL PROTECTED]> wrote:
> > The axis 1.x version of the soap monitor is pretty silent on errors -
> > I tried to fix that in axis2. In axis 1.x or axis2, look to make sure
> > nothing else is listening on port 5001 or try moving to a different
> > port to see if that helps. Double check your servlet setup in the
> > web.xml file. Firefox has an applet console which is sometimes helpful
> > in showing what the errors are.
> >
> > HTH,
> > Robert
> >
> >
> >
> >
> > On Nov 27, 2007 9:07 PM, Martin Gainty < [EMAIL PROTECTED]> wrote:
> > >
> > >
> > > Han-
> > >
> > > In axis2 soapmonitor is an independent module which is engaged to the
> > > selected service
> > > as Version is installed as as default service if you want to engage
> > > soapmonitor module for the axisService 'Version' place this in browser
> > >
> http://localhost:8080/axis2/axis2-admin/engageToService?modules=soapmonitor&axisService=Version&submit=+Engage+
> > >
> > > M--
> > >
> > >
> > > ----- Original Message -----
> > > From: Wang Han
> > > To: [email protected]
> > > Sent: Tuesday, November 27, 2007 8:47 PM
> > > Subject: Re: SOAPMonitor doesn't work after setting tomcat virtual host.
> > >
> > > Hi guys,
> > > Any clue please?
> > >
> > >
> > > On Nov 27, 2007 10:44 PM, Wang Han <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hi Vaibhav,
> > > >
> > > > "load applet failed" occurs when I use firefox.
> > > > But I can't access the SOAPMonitor either by IE -- it brings me to a
> > > > searching page immediately
> > > > with " http://localhost:8080"; in the searching bar once I try to open
> > > > the link in IE.
> > > >
> > > > I do read the appendix and deployed the service successfully before
> > > > setting the virtual host.
> > > >
> > > > After setting the virtual host, I try to re-deploy the SOAPMonitor
> > > > according to the appendix as below:
> > > > 1. compiled the SOAPMonitor class and copy them to tomcat/webapps/ROOT
> > > > 2. executing "java org.apache.axis.client.AdminClient
> > > > -lhttp://localhost:8080/AdminService deploy-monitor.wsdd "
> > > > successfully.
> > > > 3. try to find the SOAPMonitor at http://localhost:8080/SOAPMonitor,
> > > > then failed.
> > > >
> > > > Please correct me if I made any mistake here,Thanks.
> > > >
> > > >
> > > >
> > > >
> > > > On Nov 27, 2007 10:16 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
> > > > >
> > > > > I guess it should work fine with IE. If not, refer to "Appendix:
> > > Enabling the
> > > > > SOAP Monitor' under User Guide in your docs folder.
> > > > >
> > > > >
> > > > > Wang Han wrote:
> > > > > >
> > > > > > Hi guys,
> > > > > >
> > > > > > Service "echo" is deployed at:
> > > > > > http://localhost:8080/axis/services/echo, SOAPMonitor is at
> > > > > > http://localhost:8080/axis/SOAPMonitor.
> > > > > > I can use SOAPMonitor to monitor all soap messages between echo
> > > > > > service and its client.
> > > > > >
> > > > > > For some special requirement, I need re-deploy the echo service to
> > > > > > http://localhost:8080/echo .
> > > > > > I implement it successfully by modifying tomcat/conf/server.xml
> and
> > > > > > webapps/axis/web.xml.
> > > > > >
> > > > > > But the SOAPMonitor is not there any more. I  try to access it by
> > > > > > http://localhost:8080/SOAPMonitor,
> > > > > > It always gives me "load applet failed" error message.
> > > > > >
> > > > > > Could someone tell me how can I find back the SOAPMonitor? thanks
> a
> > > lot!
> > > > > >
> > > > > > Tomcat6.0 + axis1.4.
> > > > > > tomcat/conf/server.xml:
> > > > > >       <Host name="localhost"  appBase="webapps/axis"
> > > > > >             unpackWARs="true" autoDeploy="true"
> > > > > >             xmlValidation="false" xmlNamespaceAware="false">
> > > > > >          <Context path="/" docBase="."/>
> > > > > >
> > > > > > webapps/axis/WEB-INF/web.xml:
> > > > > >   <servlet-mapping>
> > > > > >    <servlet-name>AxisServlet</servlet-name>
> > > > > >    <!-- use it when need SOAPMon
> > > <url-pattern>/services/*</url-pattern>
> > > > > > -->
> > > > > >    <url-pattern>/*</url-pattern>
> > > > > >   </servlet-mapping>
> > > > > >
> > > > > >
> ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > View this message in context:
> > >
> http://www.nabble.com/SOAPMonitor-doesn%27t-work-after-setting-tomcat-virtual-host.-tf4881891.html#a13971633
> > > > > Sent from the Axis - User mailing list archive at Nabble.com .
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > 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]

Reply via email to