You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by "Puthezhath, Rajeev (TWII Boston)" <rp...@twii.net> on 2001/12/12 19:14:58 UTC

Help to run soap example.

Hi,

I am new to soap and is trying to run it with Orion server. When I try to
run the hello server example I get the following error

   Fault Code   = SOAP-ENV:Server
   Fault String = Method 'sayHelloTo' is not supported.

my service is like this

package hello;
public class HelloServer 
{
   
   public String sayHelloTo()
   {
      System.out.println("sayHelloTo(String name)");
      return "Hello " + "rajeev" + ", How are you doing?";       
   }    
}

and the client is this

 Call call = new Call();
 call.setSOAPMappingRegistry(new SOAPMappingRegistry());
     call.setTargetObjectURI("urn:Hello");
	
         call.setMethodName("sayHelloTo");
         call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);         
         Vector params = new Vector();         
	     params.addElement(new Parameter("name", String.class, name,
null));
         call.setParams(params);
		
         // Invoke the call.
         Response resp = null;         
         try
         {
            resp = call.invoke(url, "");
	
         }
   
Any idea why this is happening
Thanks
Rajeev 

What gets better performance?

Posted by Jeremy Levy <je...@yahoo.com>.
This is how I anticipate my service to be used:

>From each client:

Startup:
	1 RPC Login call
	1 RPC getting initial settings call


1 RPC Call every 15 seconds there after...


The system could eventually have thousands of simultaneous clients..

My question is, should I deploy one service with different calls or have
multiple services deployed, which will perform better?  Another way of
asking... Should each RPC Call have its own service?  Does it even matter?


JL


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


What gets better performance?

Posted by Jeremy Levy <je...@yahoo.com>.
This is how I anticipate my service to be used: