We have a pretty large Seam application and we have transactions turned on for our application.  This works for 99.9% of the application.

We have a use case where we would like to trigger processing of some data from a web action where the processing needs to be spread across multiple transactions.

We do have it working where the action delegates to a SSB with REQUIRES_NEW and things are processing correctly in their own transaction, however, the transaction started at the action level times out.  Is there any way to get the one-off case to not start a transaction before invoking an action?

Thanks,

Cory.