[EMAIL PROTECTED] (Gary VanMatre) wrote on 10/14/2005 10:20:58 PM:

> I did some more looking and you are right.  The managedBeanName of a
> nested Clay component is being ignored.
> I'll put in a fix for this one.  Good catch and thanks for your 
persistence. 
> Gary

Gary, thanks for the help.  I got the nightly build from 10/15 and now the
managedBeanName for nested clay components is working!  Great job.

I think this is really a great thing for jsf.  Now I can build a set of 
common 
components that set 75% of the attributes and then extend these on 
individual pages. 
The amount of reuse you get over conventional jsp usage really makes clay 
a wonderful 
tool.

I can package this common xml component definition is a jar file, correct? 
 I assume
I would place it in the META-INF directory and Clay would pick it up.  Is 
there any
naming convention or is Clay smart enough to pick up any file that is 
actually a 
view configuration?

Ryan

Reply via email to