It may be hard to believe, but this is almost certainly a classpath 
problem.  Your service code is loading the definition of SOAPContext 
from a different place than the RPCRouter code, so the .class of the 
two are not identical.

If you use Tomcat 4, deploy Apache SOAP as a webapp and install your 
service code within that webapp.  Instructions are at 
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-
soap/java/docs/install/tomcat.html?rev=HEAD&content-type=text/html.  
As always, also be certain that there is no soap.jar in 
$JAVA_HOME/lib/ext or $JAVA_HOME/jre/lib/ext.

On 27 Mar 2003 at 11:30, Alf Koegel wrote:

> Hi *!
> 
> I need the clients IP address on the server side.
> 
> I've read, that the onyl and one I have to do is to add a SOAPContext in the 
> server method as the first parameter. But it won't work.
> 
> - Every time I'll get 'no signature found'
> - If I delete the first parameter ( SOAPContext ) everything is ok.
> - The SOAP-Code in the RPCRouter has the correct code, it should work.
>   ( If a specified signature was not found, it will search for signature (
>     SOAPContext, oldSignature ) )
> 
> Have I missunderstoden the documentation. ( Here is a litte example code. )
> 
> ( Rem: After changing the compiled classes, I don't change the 
> DeployedServices.ds
>        file, because both use the same classname and methodname with 'urn'.  
> )
> 
> Alf Koegel
> 
> 
> _________________________________________________________________
> The new MSN 8: smart spam protection and 2 months FREE*  
> http://join.msn.com/?page=features/junkmail
> 


Scott Nichol

Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.


Reply via email to