Rick, My basic Axis installation (happyaxis, etc.) is ok. Here's my situation: First, I deployed my service by copying the class files to Axis's WEB-INF\classes directory. I ran AdminClient against AxisServlet (http://localhost:8080/axis/services/AxisServlet) using a deploy.wsdd that contains the requestFlow and responseFlow elements for soapmonitor. The service and SoapMonitor work fine. So far, so good.
However, I prefer to deploy the service by including it in a webapp, as described in the Axis docs under "Advanced Installation" (AXIS_HOME/docs/install.html#advanced). In this case, I copied the contents of Axis's web.xml into my app's web.xml, copied the Axis jar files into my app's WEB-INF/lib directory and deployed the app on Tomcat, then ran AdminClient against AxisServlet in my application (http://localhost:8080/myapp/services/AxisServlet). If deploy.wsdd does not contain the requestFlow and responseFlow elements for soapmonitor, this "add Axis to webapp" deployment works fine and I can access the service endpoint. But if deploy.wsdd contains the requestFlow and responseFlow for soapmonitor, the server throws the exception when I try to access the endpoint. The SoapMonitor link below mentioned server-config.wsdd. I'm not sure what AdminClient does with the service's config info when the service is deployed with the "add Axis to webapp" approach. I tried copying Axis's server-config.wsdd to my app's WEB-INF, then tried deleting some elements, etc., but couldn't find a permutation that worked. Regards, Mike Rick Kellogg wrote: > > Mike, > > If the server-config.wsdd file is not present then you need to deploy > the web services again. Step one: make sure HappyAxis runs correctly. > Step 2: Deploy webservices. Step 3: access ?wsdl page. Only after that > should you attempt to run the SoapMonitor. > > Good luck. > Rick > > -----Original Message----- > From: Michael Woinoski [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 19, 2003 5:05 PM > To: [EMAIL PROTECTED] > Subject: Re: enabling SOAPMonitor with Axis embedded in a web app > > Rick, > > > You are missing the entries in your web.xml file. Please review the > web.xml file contained in the axis webapp. For additional info, see: > > > http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/SoapMonito > r > > I had copied everything from the Axis web.xml and made sure everything > was > uncommented, so I don't think that's the problem. I also made sure > deploy.wsdd > contains the requestFlow and responseFlow for soapmonitor. Do I need to > create a > server-config.wsdd in the web app's WEB-INF? If so, what should it > contain? > (BTW, I'm new to Axis, so feel free to spell things out ;-) > > Thanks, > Mike > > > > > Take care, > > Rick Kellogg > > > > -----Original Message----- > > From: Michael Woinoski [mailto:[EMAIL PROTECTED] > > Sent: Thursday, June 19, 2003 3:03 PM > > To: Axis User mailing list > > Subject: enabling SOAPMonitor with Axis embedded in a web app > > > > SOAPMonitor works fine if I deploy a service by copying the class > files to > > axis's WEB-INF/classes dir. But if I copy the Axis libs into my > application's > > war file and deploy my application on Tomcat, I get a server error > when using > > the service's endpoint URL. Is it possible to use SOAPMonitor if you > add Axis to > > your web app? Or should I need to use tcpmon? > > > > Here's the error: > > org.apache.axis.ConfigurationException: Can't find handler > > name:'null' type:'soapmonitor' in the registry > > > > Thanks, > > Mike > > > > -- > > > > Mike Woinoski Pine Needle Consulting > > mailto:[EMAIL PROTECTED] > > -- > > Mike Woinoski Pine Needle Consulting > mailto:[EMAIL PROTECTED] -- Mike Woinoski Pine Needle Consulting mailto:[EMAIL PROTECTED]
