[
https://issues.jboss.org/browse/SEAMJMS-5?page=com.atlassian.jira.plugin....
]
John Ament commented on SEAMJMS-5:
----------------------------------
I have some nozzle support in my local master.
1. Find a route by its ID. The ID is defined by an ID field, or the FQCN.MethodName of
the class that contains it (for interfaces).
2. enable/disable a route at runtime.
3. Check before reading/writing from JMS whether the route is enabled and act
accordingly.
4. I did separate egress and ingress route flags, so if the route is of type BOTH, then
you can turn on reads and turn off writes, or vice versa.
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
Assignee: John Ament
Fix For: 3.0.0.Beta2
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