A kind of "screen configuration" (called instances) is proposed in
Components project, which can be seen as an extension of Templates.
Screens are defined in a configuration file. You can also have different
configuration files for different Locale : appropriate screens will be loaded
according to user Locale.
There is also an "inheritance" mechanism allowing a screen to extend
another screen : you define your main screen, and derived other screens from
it, only changing what is relevant.
To no more about Components :
(main site) http://www.lifl.fr/~dumoulin/components/
(mirror) http://www.geocities.com/cedricdumoulin//components
I am currently rewriting part of the code to allows easy addition of other
"configuration file reader". Like this, it will be possible to load instances
from, for example, a database. This will also allows dynamic change of
instances. Code rewriting will not affect actual tags syntax.
Cedric
Maya Muchnik wrote:
> Hi,
> I think the screen configuration through a xml-file is made in Components
> project (see for example,
> componentInstances.xml file). It is very convenient. As you maybe know,
> the project extends ActionServlet class.
> Maya
>
> David Geary wrote:
>
> > Yes, that's a good idea, applicable for static screens.
> >
> > We should still allow for programmatic definitions, though. Servlets or
> > servlet filters are good candidates for creating dynamic screen
> > definitions.
> >
> > david
> >
> > Wong Kok Wai wrote:
> >
> > > Is it possible to define the screen definition in the
> > > struts-config.xml? I think this will be more flexible.
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Get email at your own domain with Yahoo! Mail.
> > > http://personal.mail.yahoo.com/
