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 Sanka Samaranayake <ss...@gmail.com> on 2008/02/20 12:38:55 UTC

[Axis2] Dispatching messages to AxisEndpoints

Hi,

I believe that we already have a mechanism where we dispatch to 
AxisEndpoint if the URL has that format of 
http://[host]:[port]/axis2/services/[service-name].[endpoint-name]/ . It 
this the format we all agreed on?

I would like to get this done because I believe that when dispatching, 
we should alway obtain the AxisMessage from AxisBindingMessage via 
AxisEndpoint -> AxisBinding -> AxisBindingOperation. This way policies 
which are applicable can be obtained straightaway. Further we can 
enhance the DeploymentEngine s.t. it will generate an endpoint per 
Policy alternative which means we don't have to process a message to 
figure out the applicable policy alternative (rather we can obtain it 
from the URL). I believe it will safe lot of processing overhand and we 
can support multiple policy alternatives in a more efficient manner

Thoughts ?

Thanks,
Sanka

-- 
Sanka Samaranayake
WSO2 Inc.

http://sankas.blogspot.com/
http://www.wso2.org/ 


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org

Re: [Axis2] Dispatching messages to AxisEndpoints

Posted by keith chapman <ke...@gmail.com>.
Yes I beleive we can incorporate this change without breaking any existing
stuff.

Thanks,
Keith.

On Wed, Feb 20, 2008 at 7:25 PM, Davanum Srinivas <da...@gmail.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> My 2 cents, As long as we don't change anything that works right now and
> keep supporting existing clients and services
> and this format is just an addition, i am fine.
>
> thanks,
> dims
>
> Sanka Samaranayake wrote:
> | Hi,
> |
> | I believe that we already have a mechanism where we dispatch to
> | AxisEndpoint if the URL has that format of
> | http://[host]:[port]/axis2/services/[service-name].[endpoint-name]/ . It
> | this the format we all agreed on?
> |
> | I would like to get this done because I believe that when dispatching,
> | we should alway obtain the AxisMessage from AxisBindingMessage via
> | AxisEndpoint -> AxisBinding -> AxisBindingOperation. This way policies
> | which are applicable can be obtained straightaway. Further we can
> | enhance the DeploymentEngine s.t. it will generate an endpoint per
> | Policy alternative which means we don't have to process a message to
> | figure out the applicable policy alternative (rather we can obtain it
> | from the URL). I believe it will safe lot of processing overhand and we
> | can support multiple policy alternatives in a more efficient manner
> |
> | Thoughts ?
> |
> | Thanks,
> | Sanka
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFHvDE0gNg6eWEDv1kRAl67AJoD17Nb7qa6YZQ4NWDNNQh1dX/1PwCgvIoX
> B0aeS4xFt+k7rbhqUtPe4UA=
> =duh2
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Keith Chapman
Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: [Axis2] Dispatching messages to AxisEndpoints

Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My 2 cents, As long as we don't change anything that works right now and keep supporting existing clients and services
and this format is just an addition, i am fine.

thanks,
dims

Sanka Samaranayake wrote:
| Hi,
|
| I believe that we already have a mechanism where we dispatch to
| AxisEndpoint if the URL has that format of
| http://[host]:[port]/axis2/services/[service-name].[endpoint-name]/ . It
| this the format we all agreed on?
|
| I would like to get this done because I believe that when dispatching,
| we should alway obtain the AxisMessage from AxisBindingMessage via
| AxisEndpoint -> AxisBinding -> AxisBindingOperation. This way policies
| which are applicable can be obtained straightaway. Further we can
| enhance the DeploymentEngine s.t. it will generate an endpoint per
| Policy alternative which means we don't have to process a message to
| figure out the applicable policy alternative (rather we can obtain it
| from the URL). I believe it will safe lot of processing overhand and we
| can support multiple policy alternatives in a more efficient manner
|
| Thoughts ?
|
| Thanks,
| Sanka
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFHvDE0gNg6eWEDv1kRAl67AJoD17Nb7qa6YZQ4NWDNNQh1dX/1PwCgvIoX
B0aeS4xFt+k7rbhqUtPe4UA=
=duh2
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org