On Jun 22, 2011, at 7:08 PM, Hao Lieu wrote: > i'm going to take a look into > > [OPENEJB-1579] Setup CDI TCK for TomEE
Excellent. Do you have a JIRA account? If so I'll add you to the openejb-contributors group and assign the JIRA issue to you. Here's the link: https://issues.apache.org/jira/browse/OPENEJB-1579 -David > > > > > On Tue, Jun 14, 2011 at 4:06 PM, David Blevins <[email protected]>wrote: > >> If anyone is looking for some challenging and hard work. Still some >> critical CDI work to be done. >> >> [OPENEJB-1205] Expose Stateful remove method from proxy for Scope >> management >> [OPENEJB-1579] Setup CDI TCK for TomEE >> [OPENEJB-1581] InjectionTarget replacement for EJBs >> [OPENEJB-1582] @Inject javax.validation.Validator built-in bean >> [OPENEJB-1583] @Inject javax.validation.ValidatorFactory built-in bean >> [OPENEJB-1584] @Inject Instance<java.security.Principal> built-in bean >> [OPENEJB-1587] @Remote disabled for @Stateful beans in a non @Dependent >> scope >> [OPENEJB-1588] @Interceptors invoked before @InterceptorBinding >> interceptors >> [OPENEJB-1590] @PostConstruct called after @Inject >> [OPENEJB-1591] @Inject called after @Resource, @EJB, @PersistenceContext >> and @PersistenceUnit >> [OPENEJB-1592] @Inject support for @WebService beans >> [OPENEJB-1593] SessionBean @Specializes >> [OPENEJB-1594] SessionBeans as @New beans >> >> >> Most the above have a set of failing TCK tests that relate. Those can be >> run with the 'failed.xml' testng file in the tck/cdi-embedded/ module. If >> you have that module in your IDE you can actually just open the failed.xml >> file and click 'run' like a regular unit test. The classes are listed >> individually to make commenting them out and running just one easier. >> >> -David >> >> > > > -- > H
