Ok, that's a bug. Before the HTML templates existed, the jsfid was a required attribute of the JSP tag. We need to add a better exception. Please create a bugzilla ticket with this information so that we don't loose site of it.
http://issues.apache.org/bugzilla/enter_bug.cgi?product=Struts Thanks, Gary -------------- Original message -------------- > Ok, in my application I followed your directions to implement Tiles features > using Clay. > I have the following component declared in the global clay config : > > > > > > > > Then I have the page selectServices.xml wich contains : > > > > "-//Apache Software Foundation//DTD Shale Clay View Configuration 1.0 > //EN" > "http://struts.apache.org/dtds/shale-clay-config_1_0.dtd";> > > > > > > > > > > > > > > And finally the page gabarit.html wich has a basic structure like that : > > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> > > > > > > > > > > > > > > If you run this, you will receive a NullPointerException because contenu > symbol has the null value. So I was wondering if it was a correct behavior. > > On 12/5/05, Gary VanMatre wrote: > > > > > Something maybe that should improved is when the symbol value is null > > > instead of getting a nullpointer exception maybe do like Tiles does. > > > > > > > Clay's behavior handling symbol replacement should be as follows: > > > > If a symbol is null, it will be replaced as an empty string within the > > token if the token length is greater than the symbol. > > > > > > "testing @myvalue a symbol" --> "testing a symbol " > > > > If the symbol is null and the target expression's length is zero, the > > attribute is ignored and not passed to the component. > > > > > > "@myvalue" --> N/A, ignored > > > > If a symbol is not defined, it will not be replaced with the token. > > > > "@myvalue" --> "@myvalue" > > > > Somthing that I fixed last weekend was the case sensitivity on > > symbols. HTML attributes that are not defined by a bound component using > > the jsfid attribute, are considered symbols. > > > > > > > > > > > > The HTML parser normalizes the case of attributes to lower case. The > > token replacement is now case insensitive. The example above will now work. > > > > What is the scenario that you are talking about? Please give an example. > > > > > -- > > > Alexandre Poitras > > > Québec, Canada > > > > > > > Gary > > > > > > -- > Alexandre Poitras > Québec, Canada >
