Glad to hear you are making progress. You should put your classes in %CATALINA_HOME%\webapps\soap\WEB-INF\classes. If your classes are in packages, you would have to create the directory structure under this directory to match the package name. After placing new classes in the directory, I restart Tomcat, although I don't think I've checked to determine whether this is really necessary.
Scott ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 10, 2002 4:17 PM Subject: Re: BadTargetObjectURI problem:: Please guide me !!! > > I would like to thank you Scott.... > At least I am able to run the the sample (SOAP) that is address book as > discussed in > http://www.scottnichol.com/apachesoapinstall.htm. > > Thats to you and yur website..I am sure it is going to help many more > users. > I have been trying for long time but was not able to run even the > samples...but you have been > of a great help. > > 1. Now that my sample SOAP is running suppose I want to run my own Service > and Hello file how can I do that? > 2. Please tell me exaclty where shall I compile and put my.class file in > order for my client to > access it? > > I am seeing some hope in running my own SOAP application... > please guide me... > > Thanks again > > -------------------------------------------------------------------------- ------------------------------------ > > Nishant Awasthi > Corporate Systems Database Intern > Progressive Insurance > Phone: 440-603-4055 (Work) > Cell: 330-328-0243 (Cell) > > > > > Scott Nichol > <snicholnews@scottn To: [EMAIL PROTECTED] > ichol.com> cc: (bcc: Nishant Awasthi) > Subject: Re: BadTargetObjectURI problem:: > 07/10/2002 02:48 PM Please guide me !!! > Please respond to > soap-dev > > > > > > > > Most important is the following: > > root cause > > java.lang.NoClassDefFoundError: org/apache/tomcat/logging/Logger > at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:371) > at > > Not having run Tomcat 4.0.4, I suppose this could be a bug in Tomcat, but > that seems *extremely* unlikely. Have you removed all references to Tomcat > 3.x jars from your classpath? If Tomcat 4.x somehow gets a class from a > 3.x > jar, that could cause a problem like this. > > Scott Nichol > > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, July 10, 2002 12:45 > Subject: Re: BadTargetObjectURI problem:: Please guide me !!! > > > > > > Hello Scott. > > > > As discussed in your previous mail I have successfully installed tomcat > > 4.0.4 and soap 2.2 > > and set the classpath properly. > > > > 1. Now tomcat is running properly. > > 2. I have done exaclty as discussed at site > > http://www.scottnichol.com/apachesoapinstall.htm > > 3. http://localhost:8080/soap is also running but > > when I try to http://localhost:8080/soap/admin/index.html it give me > > following error: > > > > Apache Tomcat/4.0.4 - HTTP Status 500 - Internal Server Error > > > > > -------------------------------------------------------------------------- > ------ > > > > type Exception report > > > > message Internal Server Error > > > > description The server encountered an internal error (Internal Server > > Error) that prevented it from fulfilling this request. > > > > exception > > > > javax.servlet.ServletException: Servlet.init() for servlet jsp threw > > exception > > at > > > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:94 > > 6) > > at > > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java, > > Compiled Code) > > at > > > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja > > va:214) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 66) > > at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > > at > > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > > at > > > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja > > va:190) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 66) > > at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > > at > > org.apache.catalina.core.StandardContext.invoke(StandardContext.java, > > Compiled Code) > > at > > > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 > > ) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 66) > > at > > > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. > > java:170) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 64) > > at > > > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170 > > ) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 64) > > at > > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java, > > Compiled Code) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 64) > > at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > > at > > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > > at > > > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java > > :174) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 66) > > at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > > at > > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > > at > > > org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java, > > > > > Compiled Code) > > at > > org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java, > > Compiled Code) > > at java.lang.Thread.run(Thread.java:472) > > > > root cause > > > > java.lang.NoClassDefFoundError: org/apache/tomcat/logging/Logger > > at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:371) > > at > > > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:91 > > 8) > > at > > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java, > > Compiled Code) > > at > > > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja > > va:214) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 66) > > at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > > at > > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > > at > > > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja > > va:190) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 66) > > at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > > at > > org.apache.catalina.core.StandardContext.invoke(StandardContext.java, > > Compiled Code) > > at > > > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 > > ) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 66) > > at > > > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. > > java:170) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 64) > > at > > > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170 > > ) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 64) > > at > > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java, > > Compiled Code) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 64) > > at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > > at > > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > > at > > > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java > > :174) > > at > > > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 > > 66) > > at > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > > at > > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > > at > > > org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java, > > > > > Compiled Code) > > at > > org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java, > > Compiled Code) > > at java.lang.Thread.run(Thread.java:472) > > > > Please tell me why is that. > > > > Thanks > > > > > > > -------------------------------------------------------------------------- > ------------------------------------ > > > > Nishant Awasthi > > Phone: 440-603-4055 (Work) > > Cell: 330-328-0243 (Cell) > > > > > > > > > > Scott Nichol > > <snicholnews@scottn To: > [EMAIL PROTECTED] > > ichol.com> cc: (bcc: Nishant > Awasthi) > > Subject: Re: > BadTargetObjectURI problem:: > > 07/10/2002 09:00 AM Please guide me !!! > > Please respond to > > soap-dev > > > > > > > > > > > > > > > > I would recommend SOAP 2.3.1, since it is the latest release. I have > used > > Tomcat 4.0.1 and don't know whether 4.0.4 fixes some problem I have not > yet > > encountered. Likewise, I have used Xerces 1.4.1, not 1.4.4. Actually, I > > would recommend you just use the Xerces that comes with Tomcat 4.0.x. > > > > In other words, the combination you describe should be fine, although I > > don't have experience with all the components and I would recommend a > newer > > version of SOAP. I also recommend you follow the installation > instructions > > at http://www.scottnichol.com/apachesoapinstall.htm. > > > > Scott Nichol > > > > ----- Original Message ----- > > From: <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, July 10, 2002 8:29 AM > > Subject: Re: BadTargetObjectURI problem:: Please guide me !!! > > > > > > > > > > Hello Scott.. > > > > > > I have freedom to use different version of SOAP and Tomcat. > > > Do you recommend me to use SOAP 2.2 and Tomcat 4.4 with xerces 1.4.4? > > > If yes I would like to try this combination. > > > > > > Thanks > > > Nishant > > > > > > > > > > > > > > > Scott Nichol > > > <snicholnews@scottn To: > > [EMAIL PROTECTED] > > > ichol.com> cc: (bcc: Nishant > > Awasthi) > > > Subject: Re: > > BadTargetObjectURI problem:: > > > 07/09/2002 05:03 PM Please guide me !!! > > > Please respond to > > > soap-dev > > > > > > > > > > > > > > > > > > > > > > > > > > That is an abstract URI to specify the namespace. It is OK. You have > > > successfully deployed, the error you get implies that the service > cannot > > > find the class Hello to load. > > > > > > Do you have the freedom to use another version of Apache SOAP and/or > > > another > > > version of Tomcat? Apache SOAP installs very smoothly on Tomcat 4.0. > > > > > > Scott > > > > > > ----- Original Message ----- > > > From: <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Tuesday, July 09, 2002 3:09 PM > > > Subject: Re: BadTargetObjectURI problem:: Please guide me !!! > > > > > > > > > > > > > > I am using follwing non-working link in my DeploymentDescriptor.xml > > file > > > > while depolying my web service: > > > > > > > > http://xml.apache.org/xml-soap/deployment > > > > > > > > Is non-working of this link is not creating the problem in proper > > > > deployment of the > > > > service class. > > > > > > > > this file is attached below: > > > > > > > > <dd:service xmlns:dd="http://xml.apache.org/xml-soap/deployment"; > > > > id="urn:Example2"> > > > > <dd:provider type="java" > > > > scope="Application" > > > > methods="sayHello"> > > > > <dd:java class="Hello" > > > > static="false" /> > > > > </dd:provider> > > > > <dd:faultListener> > > > > org.apache.soap.server.DOMFaultListener > > > > </dd:faultListener> > > > > <dd:mappings /> > > > > </dd:service> > > > > > > > > Thanks.... > > > > > > > > > > -------------------------------------------------------------------------- > > > ------------------------------------ > > > > > > > > Nishant Awasthi > > > > Corporate Systems Database Intern > > > > Progressive Insurance > > > > Phone: 440-603-4055 (Work) > > > > Cell: 330-328-0243 (Cell) > > > > > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED] > > > > > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
