Hi Tomi
You can call me Vineet.
If you want that your client-congif be placed any other place then you need to specify 
that in your classpath the location of the same.

My client-config.wsdd looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<deployment xmlns="http://xml.apache.org/axis/wsdd/"; 
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
 <globalConfiguration>
             <requestFlow>
                   <handler type="java:clientHandler.RequestHandler"/>
             </requestFlow>
             <responseFlow>
                   <handler type="java:clientHandler.ResponseHandler"/>
             </responseFlow>
  </globalConfiguration>
 <transport name="java" pivot="java:org.apache.axis.transport.java.JavaSender"/>
 <transport name="http" pivot="java:org.apache.axis.transport.http.HTTPSender"/>
 <transport name="local" pivot="java:org.apache.axis.transport.local.LocalSender"/>
</deployment>

Perhaps I have got the problem. Actually I was loading the classpath from the current 
directory where I had a temporary copy of the client-config.wsdd which was getting 
called up.
Thanks 

Vineet Singh,
Software Engineer,
Web Services Centre Of Excellence,
Software Engineering Technology Labs, Infosys Technologies Ltd, 
Bangalore, India
Phone: +91 80 51059504. Mobile:9886380218.
URL: http://setlabs/wscoe (Infosys Intranet)

 

-----Original Message-----
From: Dorner Thomas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 15, 2004 1:26 PM
To: '[EMAIL PROTECTED]'
Subject: AW: client side handler undeployment

Hi Vineet Singh,

what is global configuration???
Ahh I read your post again and see, you have add the handlers in the
axis.jar / client-config.wsdd

But I want to put the client-config.wsdd in another location - but it doesn
t work :(

Thanks Tomi



-----Urspr�ngliche Nachricht-----
Von: Vineet Singh [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 15. Juli 2004 09:36
An: [EMAIL PROTECTED]
Betreff: RE: client side handler undeployment


Hello Tomi,
Thanks for replying.
I was not referencing the client-config.wsdd any where in my program. I had
declared handlers in global configuration. This was invoking the handlers
for all the client calls for any service.

Vineet Singh,
Software Engineer,
Web Services Centre Of Excellence,
Software Engineering Technology Labs, Infosys Technologies Ltd, 
Bangalore, India
Phone: +91 80 51059504. Mobile:9886380218.
URL: http://setlabs/wscoe (Infosys Intranet)

 

-----Original Message-----
From: Dorner Thomas [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 15, 2004 11:34 AM
To: '[EMAIL PROTECTED]'
Subject: AW: client side handler undeployment

Hi Vineet Singh,

I am sorry, I cant help you.

But I have a question. How do you reference the client-config.wsdd
and where do you reference the client...wsdd?
Can you give me an example???


To your Problem - are you sure you kill the handler in the used
client-config.wsdd?

Thanks Tomi

-----Urspr�ngliche Nachricht-----
Von: Vineet Singh [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 15. Juli 2004 07:28
An: [EMAIL PROTECTED]
Betreff: client side handler undeployment


Hi all
I need some help in undeploying handlers on the client side. I had
deployed some handlers on the client side by adding the information of
the handler in the axis.jar clinet-config.wsdd. now in order to undeploy
the handlers I had deleted the handler part from the client-config.wsdd,
but even now the handlers get invoked when a client program runs. The
handlers were declared as global handlers. What can I do to stop the
invocation of handlers?
thanx


Vineet Singh,
Software Engineer,
Web Services Centre Of Excellence,
Software Engineering Technology Labs, Infosys Technologies Ltd, 
Bangalore, India
Phone: +91 80 51059504. Mobile:9886380218.
URL: http://setlabs/wscoe (Infosys Intranet)

 

Reply via email to