Event Mapping Observer Method Interfaces - Egress ------------------------------------------------- Key: SEAMJMS-3 URL: https://jira.jboss.org/browse/SEAMJMS-3 Project: Seam JMS Issue Type: Feature Request Components: Event Bridging Reporter: Jordan Ganoff Priority: Blocker Implement the egress routing (forwarding CDI events to a JMS destination) as per the spec. From JSR-299-20090521.pdf: 10.7. JMS event mappings An event type may be mapped to JMS topic. An event mapping is a special kind of observer method that is declared by an interface, for example: interface EventMappings { void mapLoggedInEvent(@Observes LoggedInEvent event, @Events Topic eventTopic); } Where the parameter of type Topic resolves to the following message destination: @Resource(name="java:global/env/jms/Events") @Produces @Events Topic eventTopic; The event parameter specifies the mapped event type and bindings. Every message destination representing a topic that any injected parameter resolves to is a mapped topic. An event mapping may be specified as a member of any interface. All observers of mapped event types must be asynchronous observer methods. If an observer for a mapped event type is not an asynchronous observer method, the container automatically detects the problem and treats it as a deployment prob- lem, as defined in Section 12.4, "Problems detected automatically by the container". For every event mapping, the container must: • send a message containing the serialized event and its event bindings to every mapped topic whenever an event with the mapped event type and bindings is fired, and • monitor every mapped topic for messages containing events of that mapped event type and bindings and notify all loc- al observers whenever a message containing an event is received. Thus, events with the mapped event type and bindings are distributed to other processes which have the same event map- ping.

Event Mapping Observer Method Interfaces - Egress ------------------------------------------------- Key: SEAMJMS-3 URL: https://issues.jboss.org/browse/SEAMJMS-3 Project: Seam JMS Issue Type: Feature Request Components: Event Bridging Reporter: Jordan Ganoff Assignee: John Ament Priority: Blocker Fix For: 3.0.0.Alpha2 Original Estimate: 1 day Remaining Estimate: 1 day Implement the egress routing (forwarding CDI events to a JMS destination) as per the spec. From JSR-299-20090521.pdf: 10.7. JMS event mappings An event type may be mapped to JMS topic. An event mapping is a special kind of observer method that is declared by an interface, for example: interface EventMappings { void mapLoggedInEvent(@Observes LoggedInEvent event, @Events Topic eventTopic); } Where the parameter of type Topic resolves to the following message destination: @Resource(name="java:global/env/jms/Events") @Produces @Events Topic eventTopic; The event parameter specifies the mapped event type and bindings. Every message destination representing a topic that any injected parameter resolves to is a mapped topic. An event mapping may be specified as a member of any interface. All observers of mapped event types must be asynchronous observer methods. If an observer for a mapped event type is not an asynchronous observer method, the container automatically detects the problem and treats it as a deployment prob- lem, as defined in Section 12.4, "Problems detected automatically by the container". For every event mapping, the container must: • send a message containing the serialized event and its event bindings to every mapped topic whenever an event with the mapped event type and bindings is fired, and • monitor every mapped topic for messages containing events of that mapped event type and bindings and notify all loc- al observers whenever a message containing an event is received. Thus, events with the mapped event type and bindings are distributed to other processes which have the same event map- ping.

Event Mapping Observer Method Interfaces - Egress ------------------------------------------------- Key: SEAMJMS-3 URL: https://issues.jboss.org/browse/SEAMJMS-3 Project: Seam JMS Issue Type: Feature Request Components: Event Bridging Reporter: Jordan Ganoff Assignee: John Ament Priority: Blocker Fix For: 3.0.0.Alpha2 Original Estimate: 1 day Remaining Estimate: 1 day Implement the egress routing (forwarding CDI events to a JMS destination) as per the spec. From JSR-299-20090521.pdf: 10.7. JMS event mappings An event type may be mapped to JMS topic. An event mapping is a special kind of observer method that is declared by an interface, for example: interface EventMappings { void mapLoggedInEvent(@Observes LoggedInEvent event, @Events Topic eventTopic); } Where the parameter of type Topic resolves to the following message destination: @Resource(name="java:global/env/jms/Events") @Produces @Events Topic eventTopic; The event parameter specifies the mapped event type and bindings. Every message destination representing a topic that any injected parameter resolves to is a mapped topic. An event mapping may be specified as a member of any interface. All observers of mapped event types must be asynchronous observer methods. If an observer for a mapped event type is not an asynchronous observer method, the container automatically detects the problem and treats it as a deployment prob- lem, as defined in Section 12.4, "Problems detected automatically by the container". For every event mapping, the container must: • send a message containing the serialized event and its event bindings to every mapped topic whenever an event with the mapped event type and bindings is fired, and • monitor every mapped topic for messages containing events of that mapped event type and bindings and notify all loc- al observers whenever a message containing an event is received. Thus, events with the mapped event type and bindings are distributed to other processes which have the same event map- ping.