[
http://jira.jboss.com/jira/browse/JBMESSAGING-264?page=all ]
Tim Fox updated JBMESSAGING-264:
--------------------------------
Summary: Message bridge (was: Provide a mechanism to forward messages from one
destination to another automatically)
Description:
Provide a mechanism to forward messages from one destination to another automatically
I have had requests for this feature many times. Basically, people seem to want to be
able to have a component in messaging that will automatically forward messages to another
destination. This destination could be in the same messaging server or some remote
destination. I'm thinking that the process must either be a daemon or an MDB, and
since JBossMsg will also be available standalone I'm thinking we make it an MBean.
Another KEY to making this work is the 2PC stuff from Arjuna which isn't there yet (to
make the pop and the push transactional).
was:I have had requests for this feature many times. Basically, people seem to want to
be able to have a component in messaging that will automatically forward messages to
another destination. This destination could be in the same messaging server or some
remote destination. I'm thinking that the process must either be a daemon or an MDB,
and since JBossMsg will also be available standalone I'm thinking we make it an MBean.
Another KEY to making this work is the 2PC stuff from Arjuna which isn't there yet
(to make the pop and the push transactional).
Message bridge
--------------
Key: JBMESSAGING-264
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-264
Project: JBoss Messaging
Issue Type: Feature Request
Reporter: Chris DeLashmutt
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.Beta2
Provide a mechanism to forward messages from one destination to another automatically
I have had requests for this feature many times. Basically, people seem to want to be
able to have a component in messaging that will automatically forward messages to another
destination. This destination could be in the same messaging server or some remote
destination. I'm thinking that the process must either be a daemon or an MDB, and
since JBossMsg will also be available standalone I'm thinking we make it an MBean.
Another KEY to making this work is the 2PC stuff from Arjuna which isn't there yet (to
make the pop and the push transactional).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira