I just pulled the
latest nightly build and found some new behaviour in the way an included
backing bean is being addressed.
Each of our JSP
pages includes a page snippet (jspf) which renders a tab menu. The menu is
generated dynamically from a backing bean in request scope by binding
a panelGrid to the backing bean and generating the tab menu when the
binding is called. This has worked fine until now, however, the lastest
snapshot has changed how this happens. Now, it appears that the menu backing
bean is created and cached and the binding is called only in the model update
phase of the life cycle and not called again as the new page is being rendered.
As the menu was being created as the binding is called, our menus are no loinger
getting rendered.
Is there a reason
for this change? Has there actually been a change or is there something else
which could engender this new behaviour? Maybe a better question would be: what
is the appropriate method to create dynamic components in backing beans -- as
the binding is called (no longer works), in a constructor (potentially called
multiple times), on access of an associated property (works but seems to be a
bit of a hack).
Thanks
Julian
