Your approach is certainly viable and pretty simple, and it has occurred to me
as a possible solution. Of course, I would argue a lot of the solutions
provided by Seam could be accomplished through clever persistence mechanisms as
well.
My question therefore was meant to address the possibil
Personally, I would consider this a data issue, not so much a framework issue.
Just put a "completed" field in your Order entity that is only set when the
order is completed.
Then you can call "select * from orders o where completed = null" or whatever
to see the incompleted orders.
Reading Chapter 6 of the documentation now. Thanks, Gavin.
How could I access the conversationList object in code? This would be useful
for me so that if the user logs off, then I could persist the data related to
the conversations and then retrieve later at next logon so the user could see
w
Yes it is totally possible.
"jump to new": propagation="none"
"list of unfinished": conversationList
There is plenty of info about these features in the documentation.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052312#4052312
Reply to the post :
http:/
