You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Erik Pieczkowski (JIRA)" <ji...@apache.org> on 2008/01/23 21:31:05 UTC
[jira] Created: (TILES-240) Empty declaration
is of type Attribute rather than ListAttribute
Empty <put-list-attribute> declaration is of type Attribute rather than ListAttribute
--------------------------------------------------------------------------------------
Key: TILES-240
URL: https://issues.apache.org/struts/browse/TILES-240
Project: Tiles
Issue Type: Bug
Components: tiles-api, tiles-core
Affects Versions: 2.0.5
Environment: Windows XP, Glassfish 2, Java 5.
Reporter: Erik Pieczkowski
A Tiles definition such as...
<definition name="some.layout"
template="/WEB-INF/view/tiles/layouts/someLayout.jsp">
<put-list-attribute name="list" />
</definition>
will return an Attribute instance when calling...
Attribute fieldListAttribute = attributeContext.getAttribute("list");
whereas a tiles definition with such as...
<definition name="some.layout" template="/WEB-INF/view/tiles/layouts/someLayout.jsp">
<put-list-attribute name="list">
<add-attribute value="some.attribute" />
</put-list-attribute>
</definition>
will return a ListAttribute instance when calling that same method.
These two separate scenarios seem like they should return the same object instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TILES-240) Empty declaration
is of type Attribute rather than ListAttribute
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli closed TILES-240.
----------------------------------
> Empty <put-list-attribute> declaration is of type Attribute rather than ListAttribute
> --------------------------------------------------------------------------------------
>
> Key: TILES-240
> URL: https://issues.apache.org/struts/browse/TILES-240
> Project: Tiles
> Issue Type: Bug
> Components: tiles-api, tiles-core
> Affects Versions: 2.0.5
> Environment: Windows XP, Glassfish 2, Java 5.
> Reporter: Erik Pieczkowski
> Assignee: Antonio Petrelli
>
> A Tiles definition such as...
> <definition name="some.layout"
> template="/WEB-INF/view/tiles/layouts/someLayout.jsp">
> <put-list-attribute name="list" />
> </definition>
> will return an Attribute instance when calling...
> Attribute fieldListAttribute = attributeContext.getAttribute("list");
> whereas a tiles definition with such as...
> <definition name="some.layout" template="/WEB-INF/view/tiles/layouts/someLayout.jsp">
> <put-list-attribute name="list">
> <add-attribute value="some.attribute" />
> </put-list-attribute>
> </definition>
> will return a ListAttribute instance when calling that same method.
> These two separate scenarios seem like they should return the same object instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TILES-240) Empty declaration
is of type Attribute rather than ListAttribute
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli resolved TILES-240.
------------------------------------
Resolution: Cannot Reproduce
Fix Version/s: 2.0.6
I added some test cases to be sure, but it appears that an empty <put-list-attribute> produces a ListAttribute instance.
> Empty <put-list-attribute> declaration is of type Attribute rather than ListAttribute
> --------------------------------------------------------------------------------------
>
> Key: TILES-240
> URL: https://issues.apache.org/struts/browse/TILES-240
> Project: Tiles
> Issue Type: Bug
> Components: tiles-api, tiles-core
> Affects Versions: 2.0.5
> Environment: Windows XP, Glassfish 2, Java 5.
> Reporter: Erik Pieczkowski
> Assignee: Antonio Petrelli
> Fix For: 2.0.6
>
>
> A Tiles definition such as...
> <definition name="some.layout"
> template="/WEB-INF/view/tiles/layouts/someLayout.jsp">
> <put-list-attribute name="list" />
> </definition>
> will return an Attribute instance when calling...
> Attribute fieldListAttribute = attributeContext.getAttribute("list");
> whereas a tiles definition with such as...
> <definition name="some.layout" template="/WEB-INF/view/tiles/layouts/someLayout.jsp">
> <put-list-attribute name="list">
> <add-attribute value="some.attribute" />
> </put-list-attribute>
> </definition>
> will return a ListAttribute instance when calling that same method.
> These two separate scenarios seem like they should return the same object instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TILES-240) Empty declaration
is of type Attribute rather than ListAttribute
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli reassigned TILES-240:
--------------------------------------
Assignee: Antonio Petrelli
> Empty <put-list-attribute> declaration is of type Attribute rather than ListAttribute
> --------------------------------------------------------------------------------------
>
> Key: TILES-240
> URL: https://issues.apache.org/struts/browse/TILES-240
> Project: Tiles
> Issue Type: Bug
> Components: tiles-api, tiles-core
> Affects Versions: 2.0.5
> Environment: Windows XP, Glassfish 2, Java 5.
> Reporter: Erik Pieczkowski
> Assignee: Antonio Petrelli
>
> A Tiles definition such as...
> <definition name="some.layout"
> template="/WEB-INF/view/tiles/layouts/someLayout.jsp">
> <put-list-attribute name="list" />
> </definition>
> will return an Attribute instance when calling...
> Attribute fieldListAttribute = attributeContext.getAttribute("list");
> whereas a tiles definition with such as...
> <definition name="some.layout" template="/WEB-INF/view/tiles/layouts/someLayout.jsp">
> <put-list-attribute name="list">
> <add-attribute value="some.attribute" />
> </put-list-attribute>
> </definition>
> will return a ListAttribute instance when calling that same method.
> These two separate scenarios seem like they should return the same object instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TILES-240) Empty declaration
is of type Attribute rather than ListAttribute
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli updated TILES-240:
-----------------------------------
Fix Version/s: (was: 2.0.6)
> Empty <put-list-attribute> declaration is of type Attribute rather than ListAttribute
> --------------------------------------------------------------------------------------
>
> Key: TILES-240
> URL: https://issues.apache.org/struts/browse/TILES-240
> Project: Tiles
> Issue Type: Bug
> Components: tiles-api, tiles-core
> Affects Versions: 2.0.5
> Environment: Windows XP, Glassfish 2, Java 5.
> Reporter: Erik Pieczkowski
> Assignee: Antonio Petrelli
>
> A Tiles definition such as...
> <definition name="some.layout"
> template="/WEB-INF/view/tiles/layouts/someLayout.jsp">
> <put-list-attribute name="list" />
> </definition>
> will return an Attribute instance when calling...
> Attribute fieldListAttribute = attributeContext.getAttribute("list");
> whereas a tiles definition with such as...
> <definition name="some.layout" template="/WEB-INF/view/tiles/layouts/someLayout.jsp">
> <put-list-attribute name="list">
> <add-attribute value="some.attribute" />
> </put-list-attribute>
> </definition>
> will return a ListAttribute instance when calling that same method.
> These two separate scenarios seem like they should return the same object instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.