On Sun, Jun 20, 2010 at 7:57 PM, David Blevins wrote:
> Thoughts?
Good idea.
Would there be a complimentary XML element? I believe there would.
What will happen to a SFSB when a system exception has been thrown and
@SystemException(discard=false) is set? I can't envision any troubles
@interface SystemException {
/**
* Should the bean instance be discarded
*/
boolean discard() default true;
/**
* Should the transaction rollback
*/
boolean rollback() default true;
/**
* Same as @Applicatio
.org/maven2/org/apache/openejb/openejb-itests-standalone-client/3.1.2/openejb-itests-standalone-client-3.1.2.jar
-David
On Nov 2, 2009, at 10:44 AM, Quintin Beukes wrote:
Hey,
When I get a SystemException from the container during remote EJB
invocation, all future requests for the InitialContext a
>
> And the client which includes all deps and is an executable jar:
>
>
> http://repo2.maven.org/maven2/org/apache/openejb/openejb-itests-standalone-client/3.1.2/openejb-itests-standalone-client-3.1.2.jar
>
> -David
>
>
> On Nov 2, 2009, at 10:44 AM, Quintin B
4 AM, Quintin Beukes wrote:
Hey,
When I get a SystemException from the container during remote EJB
invocation, all future requests for the InitialContext are "broken".
My
exact situation (reason for causing the SystemException) is on my
fault, but
if there is another reason I think i
Hey,
When I get a SystemException from the container during remote EJB
invocation, all future requests for the InitialContext are "broken". My
exact situation (reason for causing the SystemException) is on my fault, but
if there is another reason I think it's good to recover from i
