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,
It was the third (silly!) point - i was talking to messagerouter and not rpcrouter! I changed it to talk to rpcrouter and it works fine now - Deploys and runs!! I'm still not sure though, why i should be doing this. It seems counter-intuitive... Thanks a lot for the help and for taking the time! Leena. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 21, 2002 9:24 AM To: [EMAIL PROTECTED] Subject: Re: Error deploying a Messaging Service [Virus Checked] Hi- Here's what I would check (my msg stuff looks just like yours, except I don't specify type="message", but that's probably not it.) (1) Your SoapProcessor really has no package? If it has a package, you need to specify the fully qualified name in the dd. (2) Check the server log file to see if the service is deploying correctly, because it looks like it isn't. If it isn't then that's your problem. (3) Silly, but is your client code talking to msgrouter and not rpcrouter? (4) If all else fails, you can easily add your own subclass of ConfigManager and specify it in soap.xml in the root of your webapp directory or war file. In that subclass you can look at everything that is happening during deployment and dd requests and log it to a file or wherever. This is a very valuable debugging aid for these situations, lets you control the circumstances of deployment undeployment, and also lets you pass options to your code and specialize factories and so forth for the whole app based on those options. HTH, S- Leena Janardanan <[EMAIL PROTECTED]> on 02/20/2002 05:04:06 PM Please respond to [EMAIL PROTECTED] To: 'mailing list' <[EMAIL PROTECTED]> cc: (bcc: Steve Salkin/3rd/US/AON) Subject: Error deploying a Messaging Service [Virus Checked] Hi folks,
