You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Bobak, Greg P." <Gr...@ColeNational.com> on 2003/05/15 19:59:08 UTC

Client response chain error

Does anyone know if the failure of handlers in the response chain on the
client side to invoke is a known - bug?  I can a handler to invoke on
response in the transport but not in the service!

Thanks,
Greg

Greg Bobak      
Senior Programmer Analyst 
Cole National 
http://www.thingsremembered.com 

-----Original Message-----
From: Bobak, Greg P. [mailto:GregBobak@ColeNational.com] 
Sent: Monday, May 05, 2003 8:57 AM
To: 'axis-user@ws.apache.org'
Subject: WSDD Client response chain error


Please help.  I have the following entry in my client-config.wsdd file, and
the response handler is never executed: 
<service name="TransactionBroker" provider="java:RPC"> 
     <parameter name="allowedMethods" value="sendTransaction"/> 
     <responseFlow> 
               <handler
type="java:com.cole.ws.handlers.HTTP.HTTPResponseInterogator"/> 
     </responseFlow> 
</service> 
I have it log a message when it is initialized, and can see that happen
before the request is sent, but the response is never handled.  The class
works when I put the responseFlow in the transport tags.  However, I'd like
to make this response flow work for only this service, not all of them
(there are several services deployed on this client).
Thank You for your help! 
Greg Bobak      
 


*************************Internet Email
Confidentiality***************************

Privileged/Confidential Information may be contained in this message.  If
you are not the addressee indicated in this message (or responsible for
delivery of the message to such person), you may not copy or deliver this
message to anyone. In such case, you should destroy this message and kindly
notify the sender by reply email. Please advise immediately if you or your
employer do not consent to Internet email for messages of this kind.
Opinions, conclusions and other information in this message that do not
relate to the official business of my firm shall be understood as neither
given nor endorsed by it. 
****************************************************************************
*************