On 3/2/06, Ryan Wynn <[EMAIL PROTECTED]> wrote: > On 3/2/06, Gary VanMatre <[EMAIL PROTECTED]> wrote: > > >From: "Ryan Wynn" <[EMAIL PROTECTED]> > > > > > > I am getting the following exception and though I have looked at bug > > > 37796 I still can't decide if what I am trying to do cannot be done > > > with symbol replacement or if I have made a mistake. > > > > > > The Component jsfid attribute is null. The cause is most likely a > > > missing "clayJsfid" attribute when using HTML templates and nesting > > > a clay component. It is also likely that the problem was caused by using > > > generic templates with symbol replacement of the > > > [EMAIL PROTECTED]: > > > java.lang.NullPointerException > > > > > > > What's the rest of the NullPointerException? Is there a custom message? > > What does the stack trace look like? > > > > > In my component that extends clay, clayJsfid is tied to a value > > > binding expression [EMAIL PROTECTED] and in my .html file I > > > specify the symbol managed-bean-name to be myBean. > > > > > > > > > I don't think that I've ever tried that. I think the error has to do with > > the suffix of the jsfid or clayJsfid in this case. The suffix is used to > > determine what handler should be used. You might try " [EMAIL PROTECTED]". > > > > Or, You might try to early binding option on the "clayJsfid" attribute. > > > > <component jsfid="clay" > > componentType="org.apache.shale.clay.component.Clay" > > allowBody="false"> > > <attributes> > > <set name="rendered" bindingType="VB" /> > > <set name="clayJsfid" bindingType="Early" value="RUNTIME"/> > > <set name="managedBeanName" bindingType="Early"/> > > <set name="shapeValidator" bindingType="None"/> > > </attributes> > > </component> > > > > > What exactly constitutes a generic template? > > > > > > > You should be able to answer that better than I can :-) . All templates > > are generic. You have 4 options > > (http://struts.apache.org/struts-shale/features-reusable-views.html). What > > are you specifically looking for? > > > > > > > Thanks, > > > Ryan > > > > Gary > > > > Thanks, Gary. The bindingType="Early" fixed it. I guess Clay was > looking for an extension and it was being done too late. > > My whole generic templates question came from the error msg that was > reported from the clay message bundle. I thought it was telling me > that particular the way I had configured my templates was too much for > it to handle with symbols. But I guess I was wrong, so far Clay can > handle all I can throw at it :-) >
One thing I did notice though was that Clay was interpreting some components nested within <!-- --> in a html template. I removed the whole comment block and the error went away.
