Hi Karan, OPENEJB-1590 has been changed to OPENEJB-1625
https://issues.apache.org/<https://issues.apache.org/jira/browse/OPENEJB-1625> jira/browse/OPENEJB-1625<https://issues.apache.org/jira/browse/OPENEJB-1625> I submitted a patch last night. The patch is an attachment to the JIRA. I think you'll be able to figure out by looking though the patch. you'll need 2 classes A and B, where b is a member of A, and A I made a stateless. The member b is annotated with @Injected. B has a callback method annotated with @PostConstruct, does some initialization. I think the only tricky part is the sauce that binds it all, you'll also need a resources/META-INF/beans.xml to activate the CDI, otherwise the injection won't happen, and during runtime, you'll get an error about not being able to locate some of the resources. Then a simple test class. I had an @EJB reference to A that the container injects, and I just retrieved A.b.getX() to make sure that X was initialized properly in the callback method. On Fri, Jul 8, 2011 at 4:08 PM, Karan Malhi <[email protected]> wrote: > Hi Hao Lieu, > > I was just taking a look at this JIRA issue. Was wondering if you have > had the time to take a look at it. If you have any notes/code to > share, feel free to submit a patch. > BTW, you could also jump on the IRC list #openejb @ freenode and we > can collaborate there too. Its a nice way to instantly bounce ideas > off of other members, although an email in the list is still the best > way. Meanwhile, I will try and see if I could try and understand what > is needed to setup . > > Thank you! > > On Wed, Jun 22, 2011 at 10:08 PM, Hao Lieu <[email protected]> wrote: > > i'm going to take a look into > > > > [OPENEJB-1579] Setup CDI TCK for TomEE > > > > > > > > > > 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 > > > > > > -- > > Karan Singh Malhi > twitter.com/KaranSinghMalhi > -- H
