Madhavi,
1.
This may be due to CLASSPATH too. (edit this)
2.
remove the ds/xml files from different locations, where classpath might
point to.
3. If
not get in, remove all the dds and ds and run the admin client through command
prompt.
Hope
this should work.
Mohan
- [EMAIL PROTECTED]
-----Original Message-----Hi!
From: Madhavi Thottempudi [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 19, 2003 4:17 AM
To: [EMAIL PROTECTED]
Subject: Re: SOAP-ENV:Server.BadTargetObjectURI
Neil! Thanks for UR reply. I have tried rebuilding .ds file as you said but it didn't work for me. I am stilling getting the same problem.
Any further ideas or suggestions on this problem would be very much appreciated.
best regards,
Madhavi
At 10:08 18/02/2003 -0800, you wrote:
I had a similar problem. As a last resort I removed the admin file: C:\soap2_3_1\webapps\soap\DeployedServices.ds and recreated it through the Admin Tool. This took care of my problem. I guess some how this file got corrupted.
Good Luck,
Neil
Madhavi Thottempudi wrote:
Hi!
I was trying to access SOAP from my client, and I am getting the following error:
org.caret.model.soap.clients.Client_Search: Fault Code = SOAP-ENV:Server.BadTargetObjectURI
org.caret.model.soap.clients.Client_Search: Fault String = Unable to resolve target object:
I don't have any clue, why this is happening, because it used to work fine until I updated my class files and undeployed/deployed the soap service again. I also tried switching back to my old version of classes - but it didn't work. Weird enough, both the old and new versions work on my colleague's machine but not on mine (we have same setup). Can somebody tell me what possibly might have gone wrong here???
I will appreciate any help or suggestions.
I am using:
Tomcat 4.0.4
Apache SOAP 2.3.1
best regards,
Madhavi
