(1) Depends upon what is the scope of the product list, and what is the scope of the shopping cart. Session? Conversation? Application?
Very loosely, a good first cut is to use one Seam component per conversation, and another Seam component each time you have some set of data that is not conversation-scoped. Have you looked at the DVD Store and booking demos, which implement workflows much like you describe? (2) This is for you to define! A shopping cart is often session scoped, but might be conversation scoped. A product list is often session scoped, but may be conversation scoped or even application scoped. It completely depends upon how you want your application to work when the user opens up multiple windows. My talk in London is 1.5 hours about Seam. The rest of the day focuses mainly on JBoss ON. I had a great holiday, thanks ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927478#3927478 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927478 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
