[ https://issues.jboss.org/browse/SEAMJMS-17?page=com.atlassian.jira.plugin... ] 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. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMJMS-17?page=com.atlassian.jira.plugin... ] Martin Gencur updated SEAMJMS-17: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/johnament/jms/pull/1 Later on I'll be adding new features as they appear in the Seam JMS API. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira