Create a standard way to bootstrap a CDI container outside of a Java EE environment for unit testing and other JSRs that need CDI features ------------------------------------------------------------------------------------------------------------------------------------------ Key: CDI-122 URL: https://issues.jboss.org/browse/CDI-122 Project: CDI Specification Issues Issue Type: Feature Request Components: Packaging and Deployment Affects Versions: 1.1 (Proposed) Environment: Java SE Reporter: Richard Hightower Fix For: 1.1 (Proposed) There should be a standard, minimalistic way to bootstrap a CDI container outside of Java EE. This is useful for unit testing extensions, and for other JSRs that need to do annotation processing, injection and interception. Instead of those other JSRs defining their own mechanism for annotation processing, injection and interception they can just use CDI. Also Java EE has clients (for JMS, RMI, Services). The same features on the serverside (injection, interceptions, proxying) are equally useful on the client side. There should also be some clear walls between what is included in Java SE CDI and Java EE CDI. Java SE CDI being a subset and core of Java EE CDI. This modularity should be better defined in the specification. -- 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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/cdi-dev

Create a standard way to bootstrap a CDI container outside of a Java EE environment for unit testing and other JSRs that need CDI features ------------------------------------------------------------------------------------------------------------------------------------------ Key: CDI-122 URL: https://issues.jboss.org/browse/CDI-122 Project: CDI Specification Issues Issue Type: Feature Request Components: Packaging and Deployment Environment: Java SE Reporter: Richard Hightower Assignee: Pete Muir Labels: bootstrap, client,, java_se There should be a standard, minimalistic way to bootstrap a CDI container outside of Java EE. This is useful for unit testing extensions, and for other JSRs that need to do annotation processing, injection and interception. Instead of those other JSRs defining their own mechanism for annotation processing, injection and interception they can just use CDI. Also Java EE has clients (for JMS, RMI, Services). The same features on the serverside (injection, interceptions, proxying) are equally useful on the client side. There should also be some clear walls between what is included in Java SE CDI and Java EE CDI. Java SE CDI being a subset and core of Java EE CDI. This modularity should be better defined in the specification.