DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21517>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21517 tile definition's put tag works in non-standard way when it is of the 'definition' type Summary: tile definition's put tag works in non-standard way when it is of the 'definition' type Product: Struts Version: 1.1 Final Platform: PC OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Tiles framework AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] One may assume that creating the following statement in the Tile configuration file: <put name="attrName" value="defName" type="definition"/> should imply the new 'AttributeDefinition' instance appearance in the tile context. There is even a special class implemented: 'DefinitionNameAttribute', which, I guess, has been intended to be used in this scenario. At least that is the way the other types of tile context attributes ('string', 'path') are resolved into relevant objects ('DirectStringAttribute', 'PathAttribute', etc). However, it does not work this way. Instead of the anticipated 'DefinitionNameAttribute' instance, the framework places the plain String object into the context! Maybe there is something I miss here, but at the moment I perceive it as the apparent inconsistence. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
