You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Antonio Petrelli (JIRA)" <ji...@apache.org> on 2007/09/14 21:38:35 UTC

[jira] Moved: (TILES-217) [tiles] element too restrictive

     [ https://issues.apache.org/struts/browse/TILES-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antonio Petrelli moved STR-1595 to TILES-217:
---------------------------------------------

          Component/s:     (was: Tiles 1 Plugin)
                       tiles-core
    Affects Version/s:     (was: 1.1.0)
                       2.0.4
             Workflow: Struts - editable closed status  (was: jira)
                  Key: TILES-217  (was: STR-1595)
              Project: Tiles  (was: Struts 1)

> [tiles] <item> element too restrictive
> --------------------------------------
>
>                 Key: TILES-217
>                 URL: https://issues.apache.org/struts/browse/TILES-217
>             Project: Tiles
>          Issue Type: Improvement
>          Components: tiles-core
>    Affects Versions: 2.0.4
>         Environment: Operating System: All
> Platform: PC
>            Reporter: Jakub Danilewicz
>            Assignee: Struts Developers
>            Priority: Minor
>
> In the Tiles configuration XML files it does not make sense to use subclassing 
> like below:
> <item [...] classtype="com...MenuItemSubclass"/>
> It is just because you cannot put the <setProperty [...]/> tag within the 
> item's body. Neither the standard DTD allows doing that nor Digester processes 
> it.
> In my opinion it is against the overall Struts configuration philosophy. 
> Moreover, I cannot even tell what may actually be the other usage 
> for 'classtype' attribute here.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.