we don't change the behavior of the test if it is not asked but if it is asked we could be ready.
- Romain 2012/2/20 Alan D. Cabrera <l...@toolazydogs.com> > I think that it's a bad practice to automagically change the explicit > behavior of tests. If a test needs to explicitly state a fact about itself > w/ an explicit annotation to get it to pass then that's what it should do. > > > Regards, > Alan > > > On Feb 20, 2012, at 12:07 AM, Romain Manni-Bucau wrote: > > > it is the second time we have such an issue, > > > > maybe we should scan junit/testng annotations (with a good catch if it is > > not available at the classpath) to add automatically these tests to the > > managed beans? > > > > - Romain > > > > > > ---------- Forwarded message ---------- > > From: amber <ambe...@hotmail.fr> > > Date: 2012/2/20 > > Subject: Re: openEJB fail on second test > > To: us...@openejb.apache.org > > > > > > ok @javax.annotation.ManagedBean is the right solution, working for me > too > > ^^ > > > > thx for help > > > > -- > > View this message in context: > > > http://openejb.979440.n4.nabble.com/openEJB-fail-on-second-test-tp4401889p4403405.html > > Sent from the OpenEJB User mailing list archive at Nabble.com. > >
