You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2008/05/10 23:13:55 UTC
[jira] Created: (SYNAPSE-303) Create abstract messaging transport
Create abstract messaging transport
-----------------------------------
Key: SYNAPSE-303
URL: https://issues.apache.org/jira/browse/SYNAPSE-303
Project: Synapse
Issue Type: Improvement
Components: Transports
Reporter: Andreas Veithen
Fix For: 1.3
Obviously the AMQP transport has been implemented starting from a copy of the existing JMS code. Since the amount of shared code/logic between AMQP and JMS seems to be high, it would be better to create an abstract messaging transport (or a set of shared utility classes) from which both the JMS and AMQP transports are derived. This would improve the maintainability and consistency of the code. In particular improvements that apply to both transports could be implemented in a single place.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-303) Create abstract messaging transport
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved SYNAPSE-303.
-------------------------------------
Resolution: Later
Deferring this issue since the AMQP transport is currently not under active development.
> Create abstract messaging transport
> -----------------------------------
>
> Key: SYNAPSE-303
> URL: https://issues.apache.org/jira/browse/SYNAPSE-303
> Project: Synapse
> Issue Type: Improvement
> Components: Transports
> Reporter: Andreas Veithen
> Fix For: 1.3
>
>
> Obviously the AMQP transport has been implemented starting from a copy of the existing JMS code. Since the amount of shared code/logic between AMQP and JMS seems to be high, it would be better to create an abstract messaging transport (or a set of shared utility classes) from which both the JMS and AMQP transports are derived. This would improve the maintainability and consistency of the code. In particular improvements that apply to both transports could be implemented in a single place.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org