Thanks for the quick response Mike.
I read the two options and I am in doubt about the following statement
regarding alias beans for my use case:
"Note also that component binding is not supported via "aliased" names.
Therefore the included page cannot include any component with a
"binding" attribute"
So I can't use something like:
<h:selectOneMenu binding="#{myController.myMenu}"/>
Currently I don't use facelets in my project but tiles.
I have read in the wiki that facelets does not correctly work with tree2
components. I am afraid of getting new problems when I add facelets.
Michael
-----Original Message-----
From: Mike Kienenberger [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 3. Mai 2006 16:29
To: MyFaces Discussion
Subject: Re: identical pages with only different beans?
Take a look at this url, particularly option 2 and option 3.
http://wiki.apache.org/myfaces/Creating_Composite_Components
On 5/3/06, Michael Heinen <[EMAIL PROTECTED]> wrote:
>
>
>
> I have a design/architecture question:
>
>
>
> My page contains 2 nearly identical tabs.
>
> Both contain complex components like datatables with scrollers,
multiple
> trees, iframes and a lot of buttons.
>
> The first tab contains the result of a search with master/detail view
(a
> datatable and a detail data pane).
>
> The second tab has the same layout and contains all objects that are
related
> to the selected object on the first tab.
>
> In other words this is the result of a finer search based on a
selection on
> the first tab.
>
> The corresponding jsps are nearly identical therefore. The only
visible
> difference is that some components are not rendered according to a
flag.
>
> So they differ internally only in the used backing bean instances and
> bindings.
>
>
>
> How could I implement this most suitable?
>
> Is there an alternative to copy the jsp and replace the names of the
backing
> beans?
>
>
>
> Moreover I don't want to limit the application to client side state
saving.
>
> So server side state saving should be supported due to complex
searches in
> the backend.
>
>
>
> I thought a quick (developed) solution could be to open a new browser
window
> with a new http session for the same user.
>
> But this is not possible based on a link without invalidating the
first
> session, or is it?
>
>
>
>
>
> Any help or ideas are appreciated.
>
> Michael
