You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Antonio Petrelli (JIRA)" <ji...@apache.org> on 2007/03/20 16:04:51 UTC
[jira] Commented: (TILES-138) Component scope is handled
incorrectly
[ https://issues.apache.org/struts/browse/TILES-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40624 ]
Antonio Petrelli commented on TILES-138:
----------------------------------------
IMHO I think that this "component scope" can be removed, since it is implicit that, in <tiles:importAttribute> and <tiles:useAttribute>, the original scope is "component". The destination scope won't be ever "component" itself: if it happened, what is the meaning of importing an attribute from "component" scope to "component" scope?
> Component scope is handled incorrectly
> --------------------------------------
>
> Key: TILES-138
> URL: https://issues.apache.org/struts/browse/TILES-138
> Project: Tiles
> Issue Type: Bug
> Components: tiles-core, tiles-jsp (jsp support)
> Affects Versions: 2.0.1
> Reporter: Antonio Petrelli
>
> The component scope, which id is stored inside the ComponentConstants interface, is handled in an incorrect way.
> Its only use is indice the "AttributeTagSupport.getScopeId" method, where it returns this scope id when the scope is "component", "template" or "tile".
> But this id is then used inside PageContext.setAttribute (in ImportAttributeTag and UseAttributeTag), that throws an exception if used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.