The deploy operation as part of a MEJB can be transactional (bottom line), in fact a rollback in the future could mean "undeploy".
For now just start the tx only if there is one. marcf |-----Original Message----- |From: Dain Sundstrom [mailto:[EMAIL PROTECTED]] |Sent: Friday, March 22, 2002 1:52 PM |To: marc fleury |Cc: Vesco Claudio; 'Andreas Schaefer'; |[EMAIL PROTECTED] |Subject: Re: [JBoss-dev] MEJB transactions (invoke deploy) | | |marc fleury wrote: | |> OK what you want to do is have the initialization of the Bean in the CMP |> engine (the deploy) CHECK for the presence of a transaction. SO if the |> deployment is transactional (as done with a Required in MEJB) |then you need |> to check for that transaction and only start if not present. | | |The problem is DDL is not transactional and even worse it auto commits |all other data in the transaction before the DDL is executed. | | |> It is a fix in the CMP initialization code, and that is Dain's domain. |> |> Claudio, you were right on the line that barf, really wrong on the MEJB |> solution, for penitence can you give Dain the 3 lines diff that achieves |> this behavior (only start transaction if not present in the |initialization |> of the code from Dain) | | |David, and I can fix this (David helped with this code), but why is |there a transaction. Deployment is not a transactional process; this is |why we have stop/destroy lifecycle events. | |-dain | _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
