[
https://issues.jboss.org/browse/SEAMJMS-5?page=com.atlassian.jira.plugin....
]
Pete Muir commented on SEAMJMS-5:
---------------------------------
I would follow the general CDI rule of requiring people to declare their routes upfront -
much easier to debug, tool etc. dynamic behaviour can lead to confusion for users IMO.
Of course, people can enable/disable the routes at runtime...
Add/Remove routes programmatically
----------------------------------
Key: SEAMJMS-5
URL:
https://issues.jboss.org/browse/SEAMJMS-5
Project: Seam JMS
Issue Type: Feature Request
Components: Event Bridging
Reporter: Jordan Ganoff
Original Estimate: 5 hours
Remaining Estimate: 5 hours
EventBridge should be able to add and remove routings dynamically, allowing for
contextual routings. For example, something triggers a route to be enabled (event, user
request, etc). All subsequent events that match the route will be routed accordingly. At
some later time something triggers the route to be disabled (user log off, batch process
end, etc) and the routing can be removed thus preventing any further forwarding of said
event types. Combined with the ability to qualify event types being routed this could
prove to be fairly useful.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira