I'd add one more question - is "session-per-conversation" approach suitable for shopping cart scenario: ShoppingCart instance lives for the application lifespan and persistent objects (say ProductItem) are added and removed? I'm asking because we had some problems with "session-per-conversation" concerning objects that did not have clear conversation boundaries.
Regards, Alexey --- Martin Marinschek <[EMAIL PROTECTED]> wrote: > When is Seam closing the session if the user leaves > the PC and doesn't > finish his task? > > when the servlet session is closed? > > regards, > > Martin > > On 4/4/06, Werner Punz <[EMAIL PROTECTED]> wrote: > > Mario Ivankovits schrieb: > > > > > I still think the seam way is the better, > "session in conversation" is > > > much more intuitive to work with as you can work > with your objects as > > > expected. > > > I would like to see a seam-light. A single jar > file which you can drop > > > into your tomcat and can start working with :-) > > > > > > > Yes, I think Seams biggest problem is the huge > number of dependencies > > and the configuration hell of around 3 xml files > and somewhat 40 jars. > > > > Seams biggest + is the session in conversation > filter which allows you > > to work with objects and orm sessions they way > they were originally > > intended, so that users do not run into the > dreaded object out of > > session scope problems anymore which are very > annoying. > > > > Maybe Shale could deliver something like it along > the lines, they > > already have a dialog/conversation pattern in > place. (which is badly in > > need for a graphical frontend ;-) ) > > > > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
