Hi Chinthaka,

On 12/6/05, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
>  Chathura, seems like you have forgotten some Axis2 stuff. :-)

Seems like I have ;-)

You are right the URL based dispatcher does do service dispatching.
Well i think i ll have to give it up because we havent decoupled our
dispatchers there is no way that we can get the SOAP action to overide
if operation gets dispatched by the URLDispatcher. So even if i want
to do it i cannot. Let me clean up the JIRA's

Thanks for the insight
Chathura

>
>  URLBasedDispatching *will* identify both the service and the operation, if
> the URL is in the form of
> <protocol>:<ip:port>/axis2/services/<serviceName>/<operationName>.
> This is what we do within axis2, if the service is deployed in Axis2. Even
> one can set the to EPR, without giving the operation name, so that we can
> identify only the service using that.
>  So URLBased dispatching has a chance of identifying the service as well.
> But SOAPAction, *most* of the time is meant to identify the operation.
>  So I think in the default dispatching, URLBased should come before,
> SOAPAction based.
>
>  Sorry, if I am missing sth here.
>
>  Chinthaka
>
>
>
>  Chathura Herath wrote:
>  On 12/6/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
>
>
>  On Tue, 2005-12-06 at 13:41 -0500, Chathura Herath wrote:
>
>
>  Its not the can do that i am interested in. Rather the right way to
> do. I think that SOAP action based dispatching should take precedence
> over the URI based one.
>
>  The dispatching that i am talking about is operation dispatching.
> *Not* service dispatching.(Our URL dispatcher doesn't do service
> dispatching after all).
> Its our way of doing it is if url looks like the following we take the
> last bit of string as the operation name.
>
> http://<endpoint url>/<operation name>
>
> In my view this isn't a standard way of doing dispatching. But SOAP Action
> is.
>
> This isn't a big issue and i do not believe it breaks a lot. Just my 2
> cent found while walking the code.
>
> Chathura
>
>
>
>
> --
> Chathura Herath
> http://www.bloglines.com/blog/chathurah
>
>
>


--
Chathura Herath
http://www.bloglines.com/blog/chathurah

Reply via email to