Hi Antonio, I agree that that works. In fact, both approaches function identically. That is not the issue. The only issue I was raising was how to make the SimpleMenuItem extension attributes validate properly in an IDE. Since, they are not declared in the DTD, I fear that XML validation will not be possible (without raising the errors of course).
My choice then is to either allow validation to take place and ignore any errors regarding the extension attributes -or- disable validation (with the possible negative side-effect of missing something that should have been caught by validation - not good). The annoyance of the bogus validation errors is outweighed by the value of having the rest of the page validated at design-time and so appears to be the best choice. Of course, I could always go and change all menu templates to use the bean definition approach instead - it makes no difference to the code, everything works just fine. Thanks for the response, -Rod -----Original Message----- From: Antonio Petrelli [mailto:[EMAIL PROTECTED] Sent: Monday, April 16, 2007 02:52 To: Struts Users Mailing List Subject: Re: tiles-defs.xml and extended attributes... 2007/4/13, Rod Bollinger <[EMAIL PROTECTED]>: > Is there a way to define these extended attributes in my TLD file or would > this require an extension to the tiles-config_1_3.dtd (not really > preferable)? What is the correct procedure for declaring these "extra" > attributes such that they are considered "valid"? I think that you should use <bean> instead of <item>, that takes <set-property> elements too. Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
