I don't know if this applies to you but there was one time when I was
experimenting with the config file too and I found that I could specify
the filename either via the System.property "axis.ClientConfigFile" or
by doing the following in your code:
org.apache.axis.EngineConfiguration config
= new org.apache.axis.configuration.FileProvider(
"/my_path_to/client-config.wsdd" );
MyLocator service = new MyLocator( config );
where MyLocator is a placeholder for the locator class generated for you
by WSDL2Java.
Hope that helps.
Ever
-----Original Message-----
From: GEORGE MCKINNEY [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 02, 2006 1:16 PM
To: Axis Users
Subject: (Axis 1.3) Our app includes 2 clients; how do I specify
different handlers for each?
We've got two different webservices that we want to be able to call with
clients generated by Axis 1.3, and use slightly different handlers for
each (but with more than one request handler in each case ). Because it
is likely that "two" will change over time, I'd like to make each
client's handler chain independent. What's the best way to do that?
Some experimentation leads me to believe that Axis can find a
"client-config.wsdd" anywhere in the classpath. Trying to decipher the
source leads me to believe that I could set a configuration property on
each service to specify the name of that file, but I'm in a fog about
the details. That would be my preferred option, because the client for
each service could use a uniquely named ( or located, and have the
configuration specify the package ) config file. How?
I also see a getHandlerRegistry().getHandlerChain() - which makes sense
to me from similar work with WebLogic's SOAP tools, but it isn't clear
how the org.apache.axis.handlers.BasicHandler maps to the handlers those
tools work with. Can someone explain?
Finally, there is a service element available for the .wsdd ( in
http://wiki.apache.org/ws/FrontPage/Axis/WSDDReferences/WSDD_XSD ) that
appears to be parallel to the <globalConfiguration> we use now, but the
documentation seems to suggest that it is for use server-side, rather
than for a client that is going to be using the specified Service. Am I
misunderstanding?
Thanks for your time,
George McKinney
