[cdi-dev] [JBoss JIRA] Commented: (CDI-106) Support JMS mappings
richardhightower at gmail.com
Sat Apr 30 16:07:19 EDT 2011
I'd like to see these boundaries more defined and cdi more modular and less dependent on java ee so that other JSRs even non java ee JSRs can use it.
Sent from my iPad
On Apr 30, 2011, at 12:20 PM, "Mark Struberg (JIRA)" <jira-events at lists.jboss.org> wrote:
> [ https://issues.jboss.org/browse/CDI-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599248#comment-12599248 ]
> Mark Struberg commented on CDI-106:
> There are already lots of EE specific things in the spec. But the entry section lists a possibility to run in a stripped down form if running on SE:
> "An application that takes advantage of these services may be designed to execute in either th Java EE environment or the Java SE environment. If the application uses Java EE services such as transaction management and persistence in the Java SE environment, the services are usually restricted to, at most, the subset defined for embedded usage by the EJB specification."
> The spec says that the container must know how to handle those EE resources/functionality. But the spec also allows to implement it via a lightweight modular plugin system (OWB is designed that way) where not all the functionality is always present in every deployment.
>> Support JMS mappings
>> Key: CDI-106
>> URL: https://issues.jboss.org/browse/CDI-106
>> Project: CDI Specification Issues
>> Issue Type: Feature Request
>> Reporter: Pete Muir
>> Fix For: 1.1 (Proposed)
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
More information about the cdi-dev