You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by James Chamberlain <ja...@je.jfcom.mil> on 2005/12/28 18:37:41 UTC
Can Synapse use ws-addressing to switch transports?
I am working on a project where it would be useful to have something
like Synapse route messages to more than one transport. I am looking at
using ws-addressing to tell it where to route the message. Some messages
would be destined for http endpoints and others would be destined to
endpoints that use a custom transport. I have had success with Synapse
routing the messages via ws-addressing to http endpoints, but I have not
had success with it routing to my other endpoints that use the custom
transport.
Is this a problem that Synapse is trying to solve (message routing
between different transports)?
Should this functionality be working in this pre-M1 release and I am
just doing something wrong or is this functionality not ready yet?
I know this is pre-release software and don't mind digging in to figure
out what is going on. I just wanted to sanity check that Synapse is
designed to do what I am asking it to do.
Thanks,
James
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Can Synapse use ws-addressing to switch transports?
Posted by Saminda Abeyruwan <sa...@gmail.com>.
Hi James,
You can create JIRA on Synapse now. Sorry for the inconvenience.
Thank you
Saminda
On 12/29/05, James Chamberlain <ja...@je.jfcom.mil> wrote:
>
> I tried to open a issue in JIRA for adding support for additional
> transports. It looks like the permissions on JIRA are too restrictive to
> allow me to add a new issue. Here is the error that I got:
>
> Assign To: The default assignees do NOT have ASSIGNABLE permission
> OR
> Unassigned issues are turned off.
>
> If the permissions get opened up I will add the issue.
>
> - James
>
>
> On Thu, 2005-12-29 at 10:40 +0600, Saminda Abeyruwan wrote:
> >
> >
> > On 12/28/05, James Chamberlain <ja...@je.jfcom.mil> wrote:
> > I am working on a project where it would be useful to have
> > something
> > like Synapse route messages to more than one transport. I am
> > looking at
> > using ws-addressing to tell it where to route the message.
> > Some messages
> > would be destined for http endpoints and others would be
> > destined to
> > endpoints that use a custom transport. I have had success with
> > Synapse
> > routing the messages via ws-addressing to http endpoints, but
> > I have not
> > had success with it routing to my other endpoints that use the
> > custom
> > transport.
> >
> > Is this a problem that Synapse is trying to solve (message
> > routing
> > between different transports)?
> >
> > Should this functionality be working in this pre-M1 release
> > and I am
> > just doing something wrong or is this functionality not ready
> > yet?
> >
> >
> > I know this is pre-release software and don't mind digging in
> > to figure
> > out what is going on. I just wanted to sanity check that
> > Synapse is
> > designed to do what I am asking it to do.
> >
> >
> > Thanks,
> >
> > James
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: synapse-dev-
> > help@ws.apache.org
> >
> > Hi James,
> >
> > You are absolutely right. This will be one of Synapse ultimate goals
> > {with qos like RM, Security, Transaction etc. }.
> >
> > You can definitely use WS-Addressing to switch between transport or
> > you can use <header/> element to select transport. Now Synapse is on
> > Pre-M1 stage and it's configured to route messages among HTTP
> > transports. What we are looking at the moment is to integrate JMS
> > transport as well. The current code at SVN has functionality to
> > configure HTTP transport only so we have more work ahead of us.
> >
> > We would really appreciate, if you can raise a JIRA on this aspect
> > (bug tracking tool).
> >
> > We are kindly welcome you to help us improve Synapse code base and
> > development.
> >
> > Thank you
> >
> > Saminda
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
Re: Can Synapse use ws-addressing to switch transports?
Posted by James Chamberlain <ja...@je.jfcom.mil>.
I tried to open a issue in JIRA for adding support for additional
transports. It looks like the permissions on JIRA are too restrictive to
allow me to add a new issue. Here is the error that I got:
Assign To: The default assignees do NOT have ASSIGNABLE permission OR
Unassigned issues are turned off.
If the permissions get opened up I will add the issue.
- James
On Thu, 2005-12-29 at 10:40 +0600, Saminda Abeyruwan wrote:
>
>
> On 12/28/05, James Chamberlain <ja...@je.jfcom.mil> wrote:
> I am working on a project where it would be useful to have
> something
> like Synapse route messages to more than one transport. I am
> looking at
> using ws-addressing to tell it where to route the message.
> Some messages
> would be destined for http endpoints and others would be
> destined to
> endpoints that use a custom transport. I have had success with
> Synapse
> routing the messages via ws-addressing to http endpoints, but
> I have not
> had success with it routing to my other endpoints that use the
> custom
> transport.
>
> Is this a problem that Synapse is trying to solve (message
> routing
> between different transports)?
>
> Should this functionality be working in this pre-M1 release
> and I am
> just doing something wrong or is this functionality not ready
> yet?
>
>
> I know this is pre-release software and don't mind digging in
> to figure
> out what is going on. I just wanted to sanity check that
> Synapse is
> designed to do what I am asking it to do.
>
>
> Thanks,
>
> James
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-
> help@ws.apache.org
>
> Hi James,
>
> You are absolutely right. This will be one of Synapse ultimate goals
> {with qos like RM, Security, Transaction etc. }.
>
> You can definitely use WS-Addressing to switch between transport or
> you can use <header/> element to select transport. Now Synapse is on
> Pre-M1 stage and it's configured to route messages among HTTP
> transports. What we are looking at the moment is to integrate JMS
> transport as well. The current code at SVN has functionality to
> configure HTTP transport only so we have more work ahead of us.
>
> We would really appreciate, if you can raise a JIRA on this aspect
> (bug tracking tool).
>
> We are kindly welcome you to help us improve Synapse code base and
> development.
>
> Thank you
>
> Saminda
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Can Synapse use ws-addressing to switch transports?
Posted by Saminda Abeyruwan <sa...@gmail.com>.
On 12/28/05, James Chamberlain <ja...@je.jfcom.mil> wrote:
>
> I am working on a project where it would be useful to have something
> like Synapse route messages to more than one transport. I am looking at
> using ws-addressing to tell it where to route the message. Some messages
> would be destined for http endpoints and others would be destined to
> endpoints that use a custom transport. I have had success with Synapse
> routing the messages via ws-addressing to http endpoints, but I have not
> had success with it routing to my other endpoints that use the custom
> transport.
>
> Is this a problem that Synapse is trying to solve (message routing
> between different transports)?
>
> Should this functionality be working in this pre-M1 release and I am
> just doing something wrong or is this functionality not ready yet?
>
>
> I know this is pre-release software and don't mind digging in to figure
> out what is going on. I just wanted to sanity check that Synapse is
> designed to do what I am asking it to do.
>
>
> Thanks,
>
> James
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
> Hi James,
You are absolutely right. This will be one of Synapse ultimate goals {with
qos like RM, Security, Transaction etc. }.
You can definitely use WS-Addressing to switch between transport or you can
use <header/> element to select transport. Now Synapse is on Pre-M1 stage
and it's configured to route messages among HTTP transports. What we are
looking at the moment is to integrate JMS transport as well. The current
code at SVN has functionality to configure HTTP transport only so we have
more work ahead of us.
We would really appreciate, if you can raise a JIRA on this aspect (bug
tracking tool).
We are kindly welcome you to help us improve Synapse code base and
development.
Thank you
Saminda