On Thu, Jun 18, 2009 at 8:27 AM, Carl-Eric Menzel <[email protected]> wrote: > > The idea of a "conversation" has been around for a long time. It's > > called a stateful session bean. > > You have a point there. But I think this is all provided by Wicket > already - You have components and models that perfectly encapsulate all > this. Basically this is about the lifecycle of the data needed for a > unit of work from the user's point of view. If you have a flow of > pages, or wizard steps, or whatever, you have a defined starting point > where you can, for example, create a model. And then you go to the next > step and pass this model along. Once you're finished, you just drop the > references. > > Or am I missing something here?
Yes, Wicket does have great support for stateful programming. That's why I love Wicket! However, if I can run Wicket inside a "container" that supports JSR-299 and I can have my web beans injected into my Wicket components/pages as proxies so that I'm always talking to the right bean at the right time and I don't have to worry about all that state crap (at least in the web tier), then I think that's a big win. > > Carl-Eric > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
