[
https://issues.jboss.org/browse/SEAMJMS-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Ament updated SEAMJMS-21:
------------------------------
Fix Version/s: (was: 3.0.0.Alpha2)
After doing a bit more review, the issue is more related to multiple sessions
being injected differently. using the message builder api this goes away. the
message builder api has become the core internal API for working with JMS.
> Create a MessageScoped scope.
> -----------------------------
>
> Key: SEAMJMS-21
> URL: https://issues.jboss.org/browse/SEAMJMS-21
> Project: Seam JMS
> Issue Type: Enhancement
> Components: Injection
> Reporter: John Ament
> Assignee: John Ament
>
> Currently, you can't inject HTTP bound scopes into JMS since the message
> listeners (MDBs or other MessageListener impls) are run in background
> threads. We need to introduce a MessageScoped scope that can bind to these
> background threads, so that shared objects can fall into the same scope, and
> be bound together.
--
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
