At 04:47 PM 7/13/2001 -0400, Daryl Beattie wrote:
> 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.
...
>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. :)
I'd agree it's server-side, in fact that message should only be able to
come from ServerHTTPUtils.java, and it's almost certainly happening in the
ClassNotFoundException raised by ctxt.loadClass() where ctxt is a SOAPContext
object, so you look at SOAPContext.java for loadClass() or you just figure
that you've got a classpath problem :-). One item puzzles me; you're deploying
in a jvm whose classpath you show, and your client is running in a jvm whose
classpath you show, but you didn't actually show the server classpath. I
would at this point try
(a) make sure the
ce.ready2ware.authentication.AuthenticationService
class is in a jar (I presume that's your Authentication.jar?) and actually
check for
ce/ready2ware/authentication/AuthenticationService
as a string in that jar just in case you accidentally jarred it from the
wrong directory, and then
(b) drop that jar into your JAVA_HOME's jre/lib/ext directory, which makes
it about as visible as it can be. (But it can make other programs invisible
to it; this is a question of hierarchy-of-class-loaders. sigh.)
If you already tried that, um, I dunno.
Tom Myers
