axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "keith chapman" <keithgchap...@gmail.com>
Subject Re: [AXIS2] WSDL 2 integration and Proposal for supporting multiple endpoints
Date Mon, 22 Jan 2007 05:52:40 GMT
Hi deepal,

Thanks for your comments. The WSDL can specify the formatting of the output
message based on the endpoint that the message came to. In order to format
the output message correctly we have to know which binding the message came
to. Does that answer your concern?

Thanks,
Keith

On 1/22/07, Deepal Jayasinghe <deepal@opensource.lk> wrote:
>
> Hi keith;
> Few comments from me.
>
> > Hi devs,
> >
> > As most of you might know we (Chinthaka and myself) created a branch
> > [1] to work on Axis2 to improve it for WSDL 2.0 support. We have
> > successfully completed most of the work now. The rest can be completed
> > within a week or so.  So we thought we better discuss  the  changes we
> > had to do before merging the branch to the trunk. We had to do a
> > couple of notable changes to Axis2 in order to  do the improvements in
> > a cleaner way. We did not want to hack axis2 to provide WSDL 2 support.
>
> +1
>
> >
> > In order to maximize the benefits of WSDL is it clear that axis2 needs
> > to support multiple endpoints. Currently axis2 does not support
> > multiple services or multiple endpoints. Axis2 just processors the
> > first endpoint and deploys the service. While integrating WSDL 2.0
> > support to axis2 it was clear that we needed to support multiple
> > endpoints.
>
> I can not understand why do we need to support (I mean process) multiple
> endpoint at the server side , as I know at the server side its up to the
> server to decide what are the endpoint that can support. In the wsdl you
> can say that you need to have endpoint for jms but server does not have
> capability of supporting that , so in that situation what is the server
> suppose to do with the new proposal ?
>
> >
> >
> > *Effects on Dispatching*
> >
> > With the introduction of multiple endpoints we should have a way of
> > dispatching messages to the correct endpoints now. The mechanism we
> > used was to have the default URIs as
> > $Prefix/ServiceName.EndpointName[/OperationName][/Other Stuff]. It
> > will be nice if we can include something like
> >
> > <endpoints>
> >     <endpoint alias="NSPath" name="" />*
> > </endpoints>?
> >
> > in the services.xml. which will make the request url look like
> > $Prefix/alias[/OperationName][/Other Stuff]
> >
> > We have updated RequestURIBasedDispatcher to dispatch messages to the
> > correct endpoint based on the above.
>
> I'd rather like to write a new Dispatcher to dispatch this particular
> scenario
>
> Thanks
> Deepal
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>

Mime
View raw message