The transactions for the relevant functions of this entity bean are defined
as <trans-attribute>Required</trans-attribute> in my ejb-jar.xml. (This
worked as expected in Orion, I'm pretty sure that my code is correct.)
Mike
----- Original Message -----
From: "Victor Langelo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 28, 2001 12:57 PM
Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()
> I cannot tell from your description whether the entity bean method's
transaction
> attribute is tx_supports. If it is, then JBoss should be throwing an
exception
> since setRollbackOnly isn't valid in this context.
>
> --Victor
>
> Michael Jara wrote:
>
> > FYI: I took a clue from bug #420714 an tried moving my "setRollbackOnly"
to
> > a session bean. I was doing something like this before in my entity
bean:
> >
> > this.entityContext.setRollbackOnly();
> > throw new StorageSynchronizationException(); // my application exception
> >
> > I changed the entity bean:
> >
> > // this.entityContext.setRollbackOnly();
> > throw new StorageSynchronizationException(); // my application exception
> >
> > And I added to the the stateful session bean which was calling the
entity
> > bean:
> >
> > ...
> > catch(StorageSynchronizationException ex)
> > {
> > this.sessionContext.setRollbackOnly();
> > throw ex;
> > }
> >
> > This works correctly! The problem appears to be specific to entity
beans.
> > Nevertheless, it is still a problem, but at least I have a better
> > workaround.
> >
> > Mike
> >
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
