If you have a message service, it is treated as having only one operation. (The Axis user guide or FAQ explains this.) You could make the invoked method dispatch to the various desired operations.
If you have you have a service with two ports, it should probably have two distinct address URLs in order that the right binding and operation be found without having to look at the soap body (which Axis won't do at all if there is a message-based service attached to that endpoint). It would probably be better to make both of the operations be in the same portType, binding and port, which means they should both have the same style. Jeff On 6/21/06, Stefan Kuhn <[EMAIL PROTECTED]> wrote:
Hi, as I just found out it seems the problem is the mixture of rpc and message style. The line generated in server-config.wsdd looks like this: <service name="NMRShiftDB" provider="java:MSG" use="literal"> and this gives problems with method returning a string. I either need to define them as two different services or make both services message-style. At least it seems possible. I would have put them in one service since they are closely related, but this is not necessary, so I can do this. Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
