Creating a request bean for the specific event and setting it in the action that gets fired by the JSCookMenu is fine. The reason I like to shy away from request beans is that you have to make sure that the data is always posted back, otherwise you run the risk of losing it.
On Wed, 2 Mar 2005 14:00:32 +0100, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi > > What is the best practice for the following scenario : > > I have a page that can display different events. From the menu > (JSCookMenu) you should be able select a specicif event, and be sent to > this page which in turn would display the data for that event. In good > ol' Struts you would do this through request parameters, and handle it > in the action. But since JSF is post oriented that won't work. I read > tip at the Sun JSF forum about creating a form on the page, and having a > setter on the backing been for the entire form. Then in that setter get > the request and handle it from there. Is this something that is > encouraged or is there a more elegant way of doing it? > > Hermod > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > > This email with attachments is solely for the use of the individual or > entity to whom it is addressed. Please also be aware that the DnB NOR Group > cannot accept any payment orders or other legally binding correspondence with > customers as a part of an email. > > This email message has been virus checked by the virus programs used > in the DnB NOR Group. > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > > -- -Heath Borders-Wing [EMAIL PROTECTED]
