Re: [OT] Re: Facade in the view

2005-09-20 Thread Jadeler
Thanks Dave and Michael. I've implemented the UserContainer object as a means of just encapsulating necessary info that would otherwise be in separate sessions. I have also used the action forms accordingly to display necessary info that would be more natural. For pages that require the form to

Re: [OT] Re: Facade in the view

2005-09-20 Thread Dave Newton
Michael Jouravlev wrote: It still is decoupled, only nested ;-) Nesting it in ActionForm you keep its state and get it populated from request. You can do the same for unit test: keep the state and populate. Hmm, yeah, I suppose. I guess in this case I felt that the stuff in the object in que

Re: [OT] Re: Facade in the view

2005-09-20 Thread Michael Jouravlev
On 9/20/05, Dave Newton <[EMAIL PROTECTED]> wrote: > Michael Jouravlev wrote: > > >Or... you can set Product object as nested property of an ActionForm, > >and set ActionForm's scope to "session". The result is the same, but > >seems more natural to me. You can render Product on JSP page, or > >po

[OT] Re: Facade in the view

2005-09-20 Thread Dave Newton
Michael Jouravlev wrote: Or... you can set Product object as nested property of an ActionForm, and set ActionForm's scope to "session". The result is the same, but seems more natural to me. You can render Product on JSP page, or populate it from input (Struts will do it for you). True. But

Re: Facade in the view

2005-09-20 Thread Michael Jouravlev
Or... you can set Product object as nested property of an ActionForm, and set ActionForm's scope to "session". The result is the same, but seems more natural to me. You can render Product on JSP page, or populate it from input (Struts will do it for you). Michael On 9/20/05, Jadeler <[EMAIL PROTE

Re: Facade in the view

2005-09-20 Thread Dave Newton
Jadeler wrote: To better maintain all the data, I am opting not having alot of session variables but instead maintain one object that will contain all data needed and store that in a session. [...] Do you guys do something similar or any other recommendations? I generally do something simil

Facade in the view

2005-09-20 Thread Jadeler
To better maintain all the data, I am opting not having alot of session variables but instead maintain one object that will contain all data needed and store that in a session. For example, instead of having session.setAttribute("product", product), session.setAttribute("web_preference", webPrefer