[
http://jira.jboss.com/jira/browse/JBAS-1349?page=all ]
Adrian Brock closed JBAS-1349.
------------------------------
Resolution: Deferred
Closing features that are (or will be) implemented in JBoss Messaging.
http://jira.jboss.com/jira/browse/JBMESSAGING
If anybody wants to provide a patch that implements these,
the issue can be reopened.
Duplicates of these issues will be closed
unless they provide an implementation/patch.
Patches should first be discussed in the
development forum:
http://www.jboss.com/index.html?module=bb&op=viewforum&f=153
if there isn't already a forum link attached to this issue.
Message Bridge
--------------
Key: JBAS-1349
URL:
http://jira.jboss.com/jira/browse/JBAS-1349
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
Reporter: Adrian Brock
Priority: Minor
Implementation of a MessageBridge.
----------------------------------
This is a proxy that allows messages to be sent to one JMS server
and then forwarded to the real destination.
To the senders this looks like a plain queue or topic.
This is the simplist implementation, more performant implementations are possible:
1) Implement the bridge as a new destination type within JBossMQ
2) It will behave similarly to a Queue but will not accept external receivers.
3) On a background thread (inside a JTA transaction)
take some messages from the queue and send them to the real destination.
4) The background thread should automatically recover from a failed connection
and retry at configurable intervals. Similarly it should keep retrying if
the connection cannot be instantiated at initial startup.
This is similar to what the MDB does.
--
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