To prefix: I'm using Seam extended managed transactions.

I've run into a use-case that seems to lie somewhere in the realm of 
conversations, yet doesn't quite fit current conversational semantics exactly.

Obviously conversations seem best suited to a page-to-page wizard style UI.  A 
flow with definite beginning, middle, and end that lends itself to using @Begin 
and @End.

But, what about a (potentially) long running "conversation" that does not fit 
as neatly into this pattern?  

Example:  a single view that has many forms, and thus may span many 
submit/request cycles in and of itself.  The entire usage pattern of this 
single view IS a long running conversation.  However, because you are 
explicitly making changes/actions via the multiple granular forms on this view, 
there is never a needed or logical necessity to "end" the conversation on that 
view.  You end it, really, by navigating away from the view.

To be more specific, this view's purpose is as a kind of "component builder".  
All of the actions and granular forms are working with a single component and 
its subcomponents in various ways, building and editing that component.

Thus, you could describe it as a freeform conversation rather than a directed 
conversation.  I guess that kind of gets to the heart of the question: freeform 
long running conversations vs. directed (wizard style) long running 
conversations.  Seam conversations right now seemed to be geared towards the 
latter.  I'm at odds on how best to handle the former.

Perhaps at each action on this view I should grab the UserTransaction and call 
commit on it manually?  Then, just let Seam timeout out the conversation since 
@End will never be called.  Does that sound right? 

Thoughts?

Ryan


View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912720#3912720

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912720


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to