Affects: Release Notes project_key: JBPAPP6 Currently there is no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl) in AS7. In JBoss AS 6 and earlier you could deploy the bridge as an MBean or JBoss MC bean, but the current configuration schema in AS7 simply doesn't support it. The bridge is a nice feature so we need a way to deploy it. It doesn't make sense to add the JMS bridge to a <hornetq-server> because the bridge can operate independently of a local HornetQ server. It really needs its own subsystem.
Link: Added: This issue Cloned from AS7-4268
Workflow: Removed: GIT Pull Request workflow Added: jira Security: Added: Public Docs QE Status: Added: NEW
Forum Reference: Removed: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899 Added: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899
Labels: Added: eap6_need_triage Forum Reference: Removed: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899 Added: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899
Release Notes Docs Status: Added: Not Yet Documented Affects: Added: Release Notes Forum Reference: Removed: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899 Added: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899
This issue has been triaged and decided to not block/prevent/hold the EAP 6 release. To comply with Release Criteria stating that no issues with Critical or Blocker priority setting can be open for the release, this is changed to priority Major.
Link: Added: This issue is a dependency of JBPAPP-9188
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Release Notes Text: Added: There is currently no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl). In JBoss AS 6 and earlier the bridge could be deployed as an MBean or JBoss MC bean, but the current configuration schema doesn't support it. Forum Reference: Removed: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899 Added: https://community.jboss.org/thread/195025, https://community.jboss.org/message/727899#727899
Link: Removed: This issue is a dependency of JBPAPP-9188
Labels: Removed: eap6_need_triage Added: eap601candidate
This should really be scheduled for inclusion into EAP 6.1. I don't see the version in JIRA, though.
Release Notes Docs Status: Removed: Documented as Known Issue Release Notes Text: Removed: There is currently no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl). In JBoss AS 6 and earlier the bridge could be deployed as an MBean or JBoss MC bean, but the current configuration schema doesn't support it. Docs QE Status: Removed: NEW
Link: Added: This issue relates to PRODMGT-305
Checked in EAP 6.1.0.DR4. JMS bridge can be configured there. Even when there are issues. Setting as verified.
Details inside vpn: https://post-office.corp.redhat.com/mailman/private/eap-pm-list/2013-July/msg00105.html