|Re: CompoundCommand failure results in "Transaction is already closed" IllegalStateExcepti [message #66391]
||Wed, 03 January 2007 20:51
Originally posted by: cdamus.ca.ibm.com|
This looks like a bug in the transactional command-stack implementation.
Could you please raise a bug with details (a small test case illustrating
the problem would be very helpful)?
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EMFT& ;version=1.0.2&component=Transaction&form_name=enter _bug
Jack Lynch wrote:
> I've a CompoundCommand with commands A and B. B's execute() throws a
> RuntimeException if it fails.
> When I execute it on a TransactionalCommandStack I see an
> IllegalStateException containing "Transaction is already closed".
> From what I can see in TransactionalCommandStackImpl, the handleError
> rolls back the transaction, resulting it it being closed. However the
> execute(Command, Map) method commits the transaction afterwards, and that
> is what is causing the error.
> Any ideas on how to get around this?
Powered by FUDForum
. Page generated in 0.01654 seconds