Re: [JBoss-user] SLSB atomicity

2003-07-02 Thread Ionel Gardais
Hi, thanks for all your answer. I look at my xdoclet tags and for now here is the thing : - all my CMP have the transactions set to Required, no transaction-type specified - the facade have a transaction-type set to Container and no transaction attribute sets. Assuming the following flowchart

Re: [JBoss-user] SLSB atomicity

2003-07-02 Thread Anders Engström
On Wed, Jul 02, 2003 at 09:26:40AM +0200, Ionel Gardais wrote: Hi, [snip] I have now hard coded all transaction-type=Container in all my beans (SLSB and CMP), transaction=Required in the CMP and transaction=RequiresNew in the SLSB. If your entity beans are only accessed from the facade,

[JBoss-user] SLSB atomicity

2003-07-01 Thread Ionel Gardais
Hi, I have a SLSB acting as a facade for all my CMP entities. In one of my SLSBmethods, I create two CMP beans. Is it possible to give this method an atomicity so if the first bean's creation fails, the second one shouldn't be created OR if the second bean's creation fails, the first bean

RE: [JBoss-user] SLSB atomicity

2003-07-01 Thread Rod Macpherson
Assuming the SLSB requires a transaction and the CMP create does not create a new one it should be atomic already. -Original Message- From: Ionel Gardais [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 7:51 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] SLSB atomicity Hi, I

RE: [JBoss-user] SLSB atomicity

2003-07-01 Thread Eric J Kaplan
sure in your session definition in ejb-jar.xml you specify transaction-type as container. Regards Eric -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ionel Gardais Sent: Tuesday, July 01, 2003 10:51 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] SLSB

RE: [JBoss-user] SLSB atomicity

2003-07-01 Thread Adrian Brock
Of Ionel Gardais Sent: 01 July 2003 15:51 To: [EMAIL PROTECTED] Subject: [JBoss-user] SLSB atomicity Hi, I have a SLSB acting as a facade for all my CMP entities. In one of my SLSBmethods, I create two CMP beans. Is it possible to give this method an atomicity so if the first

RE: [JBoss-user] SLSB atomicity

2003-07-01 Thread Adrian Brock
:56 To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] SLSB atomicity He is not getting an application error but rather an EJB create exception so my assumption would be he does not need to catch and rollback: set the right attributes (requires and requires existing transaction) on those

RE: [JBoss-user] SLSB atomicity

2003-07-01 Thread Rod Macpherson
: [JBoss-user] SLSB atomicity CreateException is an application exception. Adrian Brock Director of Support Back Office JBoss Group, LLC -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rod

RE: [JBoss-user] SLSB atomicity

2003-07-01 Thread Rod Macpherson
: Adrian Brock [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 8:44 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] SLSB atomicity Catch the CreateException and setRollbackOnly() on the session context. Regards, Adrian Adrian Brock Director of Support Back Office