Fellow Shale'ers,
Given the scenario when you have reference data to set up, say on the
application, which is not dependent on a particular view, but which must
be put in place before the first view is displayed, and given that there
is no single entry point for the app, what approach would you
A technique I like (and is actually used in the Use Cases example) is
to make your reference data into an application-scoped managed bean
(for stuff common to all users; use session scope if it is user
specific). Then, the first use of a value binding that needs to load
the reference data will
Right, this is more or less what I've gone for in the end, but the
managed bean I'm creating was not referenced directly in the page, and
it would have been a little artificial in that case to put it in.
So I've resorted to a createValueBinding in the Shale init() method
which bootstraps the
3 matches
Mail list logo
