By the way, a nice enhancement would be to be able to declare components in
a XML view. Something like that :
>
><view>
<component jsfid="contenuSelectServices" extends="baseContenuLayout">
<symbols>
<set name="navigation" value="/"
>/>
<set name="complement" value="/"
>/>
<set name="information"
>value="/" />
</symbols>
</component>
<component jsfid=""
>extends="baseLayout">
<symbols>
<set name="titre" value="Accueil - Portail des services
>" />
<set name="entete" value="/gabarit/entete.html" />
<set name="piv" value="/gabarit/piv.html" />
<set name="ivpied" value="/gabarit/pivpied.html" />
<set name="contenu" value="contenuSelectServices" />
</symbols>
</component>
></view>
>
>
Because right now I have to keep so many xml files just to have a template
engine with more then one level. What would be nice is to be able to define
one file per page like in Java where you have one class per file. It would
reduce the number of xml files while being more clean then the Tiles way
(one huge xml file). Do you think it a good idea and is it doable?
Try moving the "contenuSelectServices" component to the global XML config.
The globals files have issue with a jsfid that has a suffix of (.html or .xml).
I guess that you might think of this as a reverse namespace. The suffix of the
jsfid is used to determine what config handler to use (generic no .xxx suffix, .html, or .xml).
We could consider loading full view XML templates on startup but they would have to be registered
outside of the globals. Maybe another init param in the web deployment descriptor.
Please create a bugzilla enhancement ticket for this one and we will look at it for the next release.
Alexandre Poitras
Q, Canada
Gary