On Jun 11, 2008, at 5:57 PM, David Blevins wrote:
The crux of the issue is that perfectly valid approach to testing is
to treat the entire classpath and all modules in it as essentially
one big ear, the things like persistence units declared in other
jars will still be considered part of
On Tue, 2008-06-17 at 14:03 -0700, David Blevins wrote:
On Jun 17, 2008, at 12:37 AM, Martin Vysny wrote:
Probably the client identity should be removed from ThreadLocal on
Context.close(), or J2SE security (doPrivileged) could be used to hold
the principal. Should I open a bug?
Maybe
Hello!
OpenEJB is amazing to boost the development of EJB3.0.
I tried to configure OpenEJB to run in Local Mode, for debugging
purposes. When it runs, the log shows:
javax.naming.NameNotFoundException: Name jdbc_SecurityDS not found
I then tried to configure in ejb-jar.xml, but
On Jun 18, 2008, at 7:34 AM, Jaime Geovane Marcondes wrote:
Hello!
OpenEJB is amazing to boost the development of EJB3.0.
Quite a lot of effort goes into making things as easy as possible, so
we definitely appreciate the positive feedback! Thank you!
I tried to configure
Jon, this is great!
Very interesting technique on getting the OpenEJB TransactionManager
plugged into Spring. I suppose that is one of the tweaks that are
required for anything that's a subclass of
AbstractTransactionalSpringContextTests?
Hopefully I can get the doc updated in the next
