[Axis2]linking wsdl binding transport and Axis2 transports

[Srinath Perera <he...@gmail.com>]

Hi All;

This is a random thought occur to me when I am working on some system
here. Please comment :)

Even though we have done the hard work of making the transports
pluggable we have not make it final by linking the wsdl transports
define in the binding with our transports. This is what I belive we
should do.

1) register a URL with each transports, this url should be the
standard ones for transports where the SOAP binding is defined.
2) At the code generation time we should look at the repository and
accept the transprots that are registered with the repository. We
should remeber the transports in the Call and use them (if user not
overidde them).

If it is a good thing to have (and not already done :) .. while I am
away) I would like to stab at it. I can not commit when I am going to
deliver .. so If someone can do it please go ahead.

Srinath

Re: [Axis2]linking wsdl binding transport and Axis2 transports

[Srinath Perera <he...@gmail.com>]

Hi Glen;
+1 and yes .. dynamic invocations are one of the other things we need
to do for Axis2 clients
Thanks
Srinath

On 10/24/05, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hi Srinath!
>
> > This is a random thought occur to me when I am working on some system
> > here. Please comment :)
>
> Comment : +1 :)
>
> > Even though we have done the hard work of making the transports
> > pluggable we have not make it final by linking the wsdl transports
> > define in the binding with our transports. This is what I belive we
> > should do.
> >
> > 1) register a URL with each transports, this url should be the
> > standard ones for transports where the SOAP binding is defined.
> > 2) At the code generation time we should look at the repository and
> > accept the transprots that are registered with the repository. We
> > should remeber the transports in the Call and use them (if user not
> > overidde them).
>
> We should also support the case where you dynamically point at a WSDL
> and the transport is selected by looking at the binding/transport
> attribute in the WSDL.
>
> --Glen
>

Re: [Axis2]linking wsdl binding transport and Axis2 transports

[Glen Daniels <gl...@thoughtcraft.com>]

Hi Srinath!

> This is a random thought occur to me when I am working on some system
> here. Please comment :)

Comment : +1 :)

> Even though we have done the hard work of making the transports
> pluggable we have not make it final by linking the wsdl transports
> define in the binding with our transports. This is what I belive we
> should do.
> 
> 1) register a URL with each transports, this url should be the
> standard ones for transports where the SOAP binding is defined.
> 2) At the code generation time we should look at the repository and
> accept the transprots that are registered with the repository. We
> should remeber the transports in the Call and use them (if user not
> overidde them).

We should also support the case where you dynamically point at a WSDL 
and the transport is selected by looking at the binding/transport 
attribute in the WSDL.

--Glen