Something maybe that should improved is when the symbol value is null instead of getting a nullpointer exception maybe do like Tiles does.
On 12/2/05, Gary VanMatre <[EMAIL PROTECTED]> wrote: > > > > > Anyway, I now have a Template application which functionally behaves > like it was > > > > built with Tiles, meaning I have a standard page layout, and only > have to worry > > > > about the individual parts of it. Now, in Tiles I would define > definitions in > > > > the tile-config.xml file - Can I define my Clay views in the > clay-config.xml > > > > file instead of having to write an extra .xml file for each new view > (I already > > > > have to write the content (.html file))? > > > > > > > > > > Nope, If you are using full XML or HTML views as an entry point, you > have to > > define a new page. This is a reflection of how JSF create the view ID > from the > > URI. Tiles doesn't have this restriction. The full XML and HTML > templates are > > parsed on demand. If a template is changed, it is reloaded. If the > global > > config files are changes, they are reloaded and everthing else is > invalidated. > > > > Would it be possible to catch the URI that are matching component ids > > in the global file and then create the pages dynamically from there or > > the JSF specification doesn't allow that? I already use some kind of > > uri for my components ids. > > Not currently. There are three types of config handlers (generic > components, HTML and XML). Each config handler knows what type of component > it can handle. For example, if you placed a component with a jsfid of " > base.html" in the global file. It couldn't be used as a top level > component. The suffix of the jsfid defines the type of handler. The > suffixes can be overriden with a "context-param" in the web deployment > descriptor. > > We might want to think about this in the future but we probably need to > document what will be in 1.0 first. > > > Gary > > > -- Alexandre Poitras Québec, Canada
