synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saminda Wishwajith Abeyruwan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SYNAPSE-5) Add ability to route messages to transports other than http
Date Wed, 04 Jan 2006 08:00:00 GMT
    [ http://issues.apache.org/jira/browse/SYNAPSE-5?page=comments#action_12361723 ] 

Saminda Wishwajith Abeyruwan commented on SYNAPSE-5:
----------------------------------------------------

The logic of Synapse Axis2FlexibleMEPClient has changed to support routing of message among
different transports. 

If a user wants to integrate a custom transport, it will be same as integrating a transport
to Axis2. As Synapse uses Axis2, it uses Axis2's transport mechanism to exchange messages.


Using the main Axis2.xml in Synapse repository, user can configure the transports as he wish.


The current status of the logic handles REST messages as well as optimize messages. (MTOM)
. Thus, user can simply route or re-route optimize messages. 

Even though, this JIRA can be resolved with the current context, i would like to make this
open, because once with qos the logic of prior slight change. 

Concluding, Synapse-Incubating-M1-RC1 out of the box allow routing of messages among different
transports.  

> Add ability to route messages to transports other than http
> -----------------------------------------------------------
>
>          Key: SYNAPSE-5
>          URL: http://issues.apache.org/jira/browse/SYNAPSE-5
>      Project: Synapse
>         Type: Improvement
>   Components: Core
>  Environment: Synapse Pre-M1 / Axis2-0.94-SNAPSHOT / jdk 1.4.2_09
>     Reporter: James Chamberlain
>     Assignee: Saminda Wishwajith Abeyruwan

>
> Add the ability to route messages to multiple transports. Today Synapse supports routing
messages on the http transport only. It would be great if Synapse out of the box supported
all transports (http, https, jms, tcp, smtp) that are supported by Axis2. It should also support
the ability to register custom transports. The configuration should be straight forward and
preferably similar to the way transports are registered with Axis2 to reduce the learning
curve.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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


Mime
View raw message