[
https://issues.jboss.org/browse/SEAMJMS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ondrej Skutka reassigned SEAMJMS-17:
------------------------------------
Assignee: Martin Gencur
Jordan Ganoff: Let's start with something small that shows off what's
implemented to date. A small web app that uses Seam JMS to define a route
between a CDI event and a JMS destination. Other features exist but they mostly
augment the existing CDI functionality to allow the injection of JMS-related
resources (Connection, Session, Destination Producers, and Consumers) "out of
the box". It might be difficult to create a practical small example but if we
use Seam JMS to bridge event -> JMS -> event in place of doing a direct call
that could at least show its potential. One thing to note: Ingress routing
(firing events when we receive messages from JMS) is not complete so you'll
need to implement your own functionality to fire events when JMS messages are
received. You'll probably want to declare an MDB or create your own
MessageListener and simply fire the event. Once the ingress routing is complete
you can remove all that code and just define a bidirectional route.
> Create an example(s) demonstrating JMS Features
> -----------------------------------------------
>
> Key: SEAMJMS-17
> URL: https://issues.jboss.org/browse/SEAMJMS-17
> Project: Seam JMS
> Issue Type: Task
> Reporter: Ondrej Skutka
> Assignee: Martin Gencur
> Fix For: 3.0.0.Final
>
>
> Create an example(s) demonstrating JMS Features:
> - JMS resource injection
> - Event Bridge
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
