This has been solved by applying the handlers on the server-side in reverse order on the client side.

Lesson learnt: There’s nothing a little reading cant solve.

 

 

-----Original Message-----
From: Patrice Empeigne [mailto:[EMAIL PROTECTED]
Sent:
Monday, September 22, 2003 4:52 PM
To: [EMAIL PROTECTED]
Subject: client-side msgcontext objects

 

Was wondering why the following:

I have a client-side handler sitting on the global request flow. When I dump the contents of msgContext.getTargetService() from this handler, I am returned null. I also have a server-side handler sitting on the global request flow. When I dump the contents of msgContext.getTargetService() from this handler, I am returned the target service.

 

Would anyone know why this would be?

I'm trying to extract the target service and method from a SOAP request from a client side requestflow handler.

Any ideas?

 

Reply via email to