You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Daryl Beattie <Da...@screamingmedia.com> on 2001/07/13 22:47:16 UTC

SOAP-ENV:Server.BadTargetObjectURI Error

Dear SOAP-users,

        I seem to be having a little problem with SOAP. I checked the
archives for any mention of this problem, and whenever it came up it seemed
to disappear by people fiddling with their classpaths. But still, I have
been fiddling with my classpath for over a day, and still no luck. :(  I
would really like to know what the root of my problem is, so that I might
better provide a solution for it.
        What I am doing is somewhat simple. I have an EJB that is running in
JBoss-2.4.0 and Tomcat 3.2.2, and I have a SOAP 2.2 service running for it.
When I try to access the SOAP service, I get the following (which also shows
me starting the service):

C:\projects\CE3\ready2ware\build>java -cp
c:\projects\CE3\ready2ware\build\Authentication.jar;c:\xml\soap-2_2\lib\soap
.jar;c:\xml\JBoss-2.4.0_Tomcat-3.2.2\jboss\lib\ext\xerces-J_1.4.1.jar;c:\xml
\JBoss-2.4.0_Tomcat-3.2.2\jboss\lib\ext\mail.jar;c:\xml\JBoss-2.4.0_Tomcat-3
.2.2\jboss\lib\ext\activation.jar
org.apache.soap.server.ServiceManagerClient
http://localhost:8080/soap/servlet/rpcrouter deploy
c:\projects\CE3\ready2ware\src\com\screamingmedia\ce\ready2ware\authenticati
on\DeploymentDescriptor.xml

C:\projects\CE3\ready2ware\build>java -cp
c:\projects\CE3\ready2ware\build\Authentication.jar;c:\xml\soap-2_2\lib\soap
.jar;c:\xml\JBoss-2.4.0_Tomcat-3.2.2\jboss\lib\ext\xerces-J_1.4.1.jar;c:\xml
\JBoss-2.4.0_Tomcat-3.2.2\jboss\lib\ext\mail.jar;c:\xml\JBoss-2.4.0_Tomcat-3
.2.2\jboss\lib\ext\activation.jar
com.screamingmedia.ce.ready2ware.authentication.GetAuthentication
http://localhost:8080/soap/servlet/rpcrouter 3826 screamingmedia.com/
Generated fault:
  Fault Code   = SOAP-ENV:Server.BadTargetObjectURI
  Fault String = Unable to resolve target object:
ce.ready2ware.authentication.AuthenticationService
done

        I have a feeling this is a server-side problem, since I can run the
client on another machine accessing my machine, and it shoots back the same
error from there. Does anybody have any idea why this would happen? Thanks
for you help. :)

Sincerely,

        Daryl.