You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Eran Chinthaka <ch...@opensource.lk> on 2005/12/06 18:11:07 UTC
Re: [Axis2] Dispatching order.
hmm, Chathura. The dispatching order is configurable now, I think. So
you can change the default setting via the axis2.xml.
Deepal, do you want to add some more in to this ?
Chinthaka
BTW, Chathura, seems like you've forgotten the way you should send mails
to axis2 dev list.
Davanum Srinivas wrote:
>+1
>
>On 12/6/05, Chathura Herath <ch...@gmail.com> wrote:
>
>
>>Hi,
>>
>>I observed that in Axis2 Operation dispatching, the
>>RequestURLBasedDispatcher has higher precedence over
>>SOAPActionBasedDispatcher. My view is SOAP action should get
>>precedence. This is a very minor change btw.
>>Thought???
>>
>>Chathura
>>--
>>Chathura Herath
>>http://www.bloglines.com/blog/chathurah
>>
>>
>>
>
>
>--
>Davanum Srinivas : http://wso2.com/blogs/
>
>
>
Re: [Axis2] Dispatching order.
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Chathura ;
yes , have a look at phaseOrder in that xml you will be able to understand
that properly , and one more thing there are no nay difference between
Handler and dispatcher as far as Axis2 is concern , dispatcher is just a
handler.
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Chathura Herath" <ch...@gmail.com>
To: <ax...@ws.apache.org>
Sent: Wednesday, December 07, 2005 12:41 AM
Subject: Re: [Axis2] Dispatching order.
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.
Are we agreeing to this. (Sorry I just closed the JIRA hastily, will
open again if we are not converging).
I just changed the default ordering when you build the
AxisConfiguration. I guess i need to update the axis2.xml too.I
believe its the axis2.xml in
F:\Axis2\modules\core\src\org\apache\axis2\deployment that goes to the
war.
That is if we are converging.
Cheers
Chathura
On 12/6/05, Eran Chinthaka <ch...@opensource.lk> wrote:
> hmm, Chathura. The dispatching order is configurable now, I think. So you
> can change the default setting via the axis2.xml.
>
> Deepal, do you want to add some more in to this ?
>
> Chinthaka
>
> BTW, Chathura, seems like you've forgotten the way you should send mails
> to
> axis2 dev list.
>
>
> Davanum Srinivas wrote:
> +1
>
> On 12/6/05, Chathura Herath <ch...@gmail.com> wrote:
>
>
> Hi,
>
> I observed that in Axis2 Operation dispatching, the
> RequestURLBasedDispatcher has higher precedence over
> SOAPActionBasedDispatcher. My view is SOAP action should get
> precedence. This is a very minor change btw.
> Thought???
>
> Chathura
> --
> Chathura Herath
> http://www.bloglines.com/blog/chathurah
>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
>
>
--
Chathura Herath
http://www.bloglines.com/blog/chathurah
Re: [Axis2] Dispatching order.
Posted by Chathura Herath <ch...@gmail.com>.
Hi Chinthaka,
On 12/6/05, Eran Chinthaka <ch...@opensource.lk> 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 <sa...@opensource.lk> 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
Re: [Axis2] Dispatching order.
Posted by Eran Chinthaka <ch...@opensource.lk>.
Chathura, seems like you have forgotten some Axis2 stuff. :-)
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 <sa...@opensource.lk> 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
>
>
>
Re: [Axis2] Dispatching order.
Posted by Chathura Herath <ch...@gmail.com>.
On 12/6/05, Sanjiva Weerawarana <sa...@opensource.lk> 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
Re: [Axis2] Dispatching order.
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
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.
Can you explain why you think so? The reason I think URI-based dispatch
should take precedence is because its the "outermost" address ..
In any case, what problem are you trying to solve also?
Thanks,
Sanjiva.
Re: [Axis2] Dispatching order.
Posted by Chathura Herath <ch...@gmail.com>.
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.
Are we agreeing to this. (Sorry I just closed the JIRA hastily, will
open again if we are not converging).
I just changed the default ordering when you build the
AxisConfiguration. I guess i need to update the axis2.xml too.I
believe its the axis2.xml in
F:\Axis2\modules\core\src\org\apache\axis2\deployment that goes to the
war.
That is if we are converging.
Cheers
Chathura
On 12/6/05, Eran Chinthaka <ch...@opensource.lk> wrote:
> hmm, Chathura. The dispatching order is configurable now, I think. So you
> can change the default setting via the axis2.xml.
>
> Deepal, do you want to add some more in to this ?
>
> Chinthaka
>
> BTW, Chathura, seems like you've forgotten the way you should send mails to
> axis2 dev list.
>
>
> Davanum Srinivas wrote:
> +1
>
> On 12/6/05, Chathura Herath <ch...@gmail.com> wrote:
>
>
> Hi,
>
> I observed that in Axis2 Operation dispatching, the
> RequestURLBasedDispatcher has higher precedence over
> SOAPActionBasedDispatcher. My view is SOAP action should get
> precedence. This is a very minor change btw.
> Thought???
>
> Chathura
> --
> Chathura Herath
> http://www.bloglines.com/blog/chathurah
>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
>
>
--
Chathura Herath
http://www.bloglines.com/blog/chathurah