Axis Beta 2 Questoins

[Benjamin Szekely <bs...@cornell.edu>]

I was working with Axis back in october before the release and I haven't
played with it in a while so I'm trying to get caught up.  My project
involved writing new transports.  Now, in the old version, there was a
client_config.xml file which allowed me to describe the senders for the
different transports I was using.  Now, it seems that this configuration is
done dynamically in the calling code with SimpleProvider as per in the tcp
transport example.  I'd like to not have to include this code in each
calling case.  Is there an analogous client configuration WSDD in Axis Beta
2 ?
Another question I have is with the provider specified for a service.  Is
it possible to use a pivot instead of a provider so that I can use a chain
as in the old version?  Or should the provider be just the Java class and
the other memebers of my chain be included in the request_flow and
reponse_flow of the service ?

BTW, the new documentaion (The Architecture Guide) is really good.


Thanks,
Ben Szekely
bs48@cornell.edu

Re: Axis Beta 2 Questoins

[Harald Schmitt <co...@hschmitt.de>]

Hi,
you can configure your client with a file called client-config.wsdd.

Within the <wsdd:service> Element you can specify a <wsdd:typeMapping>
for custom ser/deser, a <wsdd:requestFlow>, a <wsdd:provider>, a
<wsdd:responseFlow> and a <wsdd:faultFlow> for error handling.

In <wsdd:requestFlow>, <wsdd:provider> and <wsdd:responseFlow> you can
use a chain or a handler.

You could look at the html file in the wsdd directory to view the schema
of a wsdd file.

Benjamin Szekely schrieb:
> 
> I was working with Axis back in october before the release and I haven't
> played with it in a while so I'm trying to get caught up.  My project
> involved writing new transports.  Now, in the old version, there was a
> client_config.xml file which allowed me to describe the senders for the
> different transports I was using.  Now, it seems that this configuration is
> done dynamically in the calling code with SimpleProvider as per in the tcp
> transport example.  I'd like to not have to include this code in each
> calling case.  Is there an analogous client configuration WSDD in Axis Beta
> 2 ?
> Another question I have is with the provider specified for a service.  Is
> it possible to use a pivot instead of a provider so that I can use a chain
> as in the old version?  Or should the provider be just the Java class and
> the other memebers of my chain be included in the request_flow and
> reponse_flow of the service ?
> 
> BTW, the new documentaion (The Architecture Guide) is really good.
> 
> Thanks,
> Ben Szekely
> bs48@cornell.edu