Hi ,
Sorry my fault, i wasnt clear enough - I am talking to the rpcrouter for deploying(which is where i was having trouble earlier) and the messagerouter for sending my messages..
What i found counter-intuitive was talking to the rpcrouter for the deployment of my message-style service...
Leena.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2002 11:29 AM
To: [EMAIL PROTECTED]
Subject: RE: Error deploying a Messaging Service [Virus Checked]
Hi-
Glad to help. Now, it turns out that your fix (talk to rpcrouter) was exactly
the opposite of what I meant by (3) (talk to messagerouter if you just
automatically typed rpcrouter). This _is_ counter-intuitive because it doesn't
make any sense.
The names "rpcrouter" and "messagerouter" are just conventions for the servlet
mappings, though. Please look in your web.xml and make sure that rpcrouter is
mapping to a servlet name whose type
org.apache.soap.server.http.RPCRouterServlet and messagerouter is mapping to a
servlet name whose type is org.apache.soap.server.http.MessageRouterServlet. If
your client code is actually talking to an instance of RPCRouterServlet and yet
is successfully making a message-level call, but fails to work when talking to
an instance of MessageRouterServlet, then I have no idea what is happening
there.
S-
Leena Janardanan <[EMAIL PROTECTED]> on 02/21/2002 01:56:37 PM
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc: (bcc: Steve Salkin/3rd/US/AON)
Subject: RE: Error deploying a Messaging Service [Virus Checked]
Hi Steve,
