Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-06-28 Thread Michael Jara
;[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

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-06-28 Thread Michael Jara
are correct.) Mike - Original Message - From: "Victor Langelo" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 28, 2001 12:31 PM Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly() > Michael Jara wrote: > > > Yes, Sybase ASE

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-06-28 Thread Michael Jara
> quick question do new resources enroll in it none the less? > > the LW is normal but what would you expect (you want and /or spec) > > marcf > > |-----Original Message- > |From: [EMAIL PROTECTED] > |[mailto:[EMAIL PROTECTED]]On Behalf Of Michael Jara > |Sent: Thursda

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-06-28 Thread Victor Langelo
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 m

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-06-28 Thread Victor Langelo
Michael Jara wrote: > Yes, Sybase ASE is case sensitive as to table and column names. (SQL > keywords may be any case.) I beleive this is not unique to Sybase, but is > also the case in some other database servers such as Oracle. JAWS in JBoss > 2.2.2 works properly, but Beta 2.4 does not...

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-06-28 Thread Michael Jara
ne 28, 2001 11:05 AM Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly() > Yes, Sybase ASE is case sensitive as to table and column names. (SQL > keywords may be any case.) I beleive this is not unique to Sybase, but is > also the case in some other database servers suc

RE: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-06-28 Thread marc fleury
EMAIL PROTECTED]]On Behalf Of Michael Jara |Sent: Thursday, June 28, 2001 1:05 PM |To: [EMAIL PROTECTED] |Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly() | | |Yes, Sybase ASE is case sensitive as to table and column names. (SQL |keywords may be any case.) I beleive this is not uniq

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-06-28 Thread Michael Jara
; To: <[EMAIL PROTECTED]> Sent: Wednesday, June 27, 2001 11:02 PM Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly() > Michael Jara wrote: > > > I've run into a problem previously mentioned in the archives here: > > http://www.mail-archive.com/jboss-user@

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-06-27 Thread danch
Michael Jara wrote: > I've run into a problem previously mentioned in the archives here: > http://www.mail-archive.com/jboss-user@lists.sourceforge.net/msg03141.html > > > > Does anyone have a good workaround for this (aside from "don't use > setRollbackOnly", or "hack TxCapsule and build i

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-06-27 Thread Michael Jara
I've run into a problem previously mentioned in the archives here: http://www.mail-archive.com/jboss-user@lists.sourceforge.net/msg03141.html   Does anyone have a good workaround for this (aside from "don't use setRollbackOnly", or "hack TxCapsule and build it yourself"?)  This seems like a p

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-04-29 Thread Achim Demelt
e 2.3 developer version. Achim - Original Message - From: "danch" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 27, 2001 8:33 PM Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly() > I'll put together a little sample and look i

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-04-27 Thread danch
I'll put together a little sample and look into this. By my reading of the spec, you should be able to call into the bean (even the same instance) after you call setRollbackOnly and throw an application exception. Even if that weren't legal, locking-waiting would not be what we'd want to see. -d

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-04-25 Thread Achim Demelt
> What version of JBoss is this? > 2.2 binary distribution w/ tomcat 3.2.1 > The Classification that's being passed in is null, correct? Otherwise > commenting out the call to setRollbackOnly should have no effect. > Yes, it's null. Oops, I see I've copied the wrong method into the email, but

Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-04-25 Thread danch
What version of JBoss is this? The Classification that's being passed in is null, correct? Otherwise commenting out the call to setRollbackOnly should have no effect. The test client calls the entity directly (not through a session wrapper), correct? -danch Achim Demelt wrote: > > hi, > > I

[JBoss-user] LOCKING-WAITING after setRollbackOnly()

2001-04-25 Thread Achim Demelt
hi, I have a CMP entity bean and a simple test client. one of the bean methods is public void setClassification(Classification param) throws LocalizedAppEventException { if (param == null) { ctx.setRollbackOnly(); throw new LocalizedAppEventException("isis.masterdata.invalidClassificat