Is there a way from keeping *nested* conversations from locking the entire conversation stack? Is there a way to isolate the lock to only the nested conversation's scope?
Here's some background info:
I have a page that pops up a new window which begins a nested conversation. The new (nested) window performs a long transaction (up to 30sec). While this page is loading, I'd like my users to continue working on the parent window. However, this does not seem possible because Seam locks the entire conversation stack until the nested conversation is done processing the request.
I know that I can set concurrent-request-timeout to a low number and have a temporary conversation auto-magically created but this is not acceptable for this particular use case. The parent conversation contains critical information at this stage of my application.