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/02/19 14:53:15 UTC
[jira] Created: (TILES-115) MutableTilesContainer.register should
have a "TilesRequestContext" parameter
MutableTilesContainer.register should have a "TilesRequestContext" parameter
----------------------------------------------------------------------------
Key: TILES-115
URL: https://issues.apache.org/struts/browse/TILES-115
Project: Tiles
Issue Type: Improvement
Components: tiles-api, tiles-core
Affects Versions: 2.0.0
Reporter: Antonio Petrelli
Fix For: 2.0.x
Currently the MutableTilesContainer.register method has only a TileDefinition parameter, but a TilesRequestContext parameter is necessary for two reasons:
1) In Tiles 1.x a custom definition lies in request context and to provide compatibility this should be its behaviour.
2) CachingKeyedDefinitionsFactoryTilesContainer stores a DefinitionManager for each key (calculated from a TilesRequestContext), therefore it cannot know which is the key to use to retrieve the correct DefinitionManager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TILES-115) MutableTilesContainer.register methods
should have a request parameters
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli updated TILES-115:
-----------------------------------
Component/s: (was: tiles-core)
Description:
Currently the MutableTilesContainer.register method has only a TileDefinition parameter, but a request parameters (the pair "request-response" or "PageContext") are necessary for two reasons:
1) In Tiles 1.x a custom definition lies in request context and to provide compatibility this should be its behaviour.
2) CachingKeyedDefinitionsFactoryTilesContainer stores a DefinitionManager for each key (calculated from a TilesRequestContext), therefore it cannot know which is the key to use to retrieve the correct DefinitionManager.
was:
Currently the MutableTilesContainer.register method has only a TileDefinition parameter, but a TilesRequestContext parameter is necessary for two reasons:
1) In Tiles 1.x a custom definition lies in request context and to provide compatibility this should be its behaviour.
2) CachingKeyedDefinitionsFactoryTilesContainer stores a DefinitionManager for each key (calculated from a TilesRequestContext), therefore it cannot know which is the key to use to retrieve the correct DefinitionManager.
Summary: MutableTilesContainer.register methods should have a request parameters (was: MutableTilesContainer.register should have a "TilesRequestContext" parameter)
Give genericity to the problem
> MutableTilesContainer.register methods should have a request parameters
> -----------------------------------------------------------------------
>
> Key: TILES-115
> URL: https://issues.apache.org/struts/browse/TILES-115
> Project: Tiles
> Issue Type: Improvement
> Components: tiles-api
> Affects Versions: 2.0.0
> Reporter: Antonio Petrelli
> Assigned To: Antonio Petrelli
> Fix For: 2.0.x
>
>
> Currently the MutableTilesContainer.register method has only a TileDefinition parameter, but a request parameters (the pair "request-response" or "PageContext") are necessary for two reasons:
> 1) In Tiles 1.x a custom definition lies in request context and to provide compatibility this should be its behaviour.
> 2) CachingKeyedDefinitionsFactoryTilesContainer stores a DefinitionManager for each key (calculated from a TilesRequestContext), therefore it cannot know which is the key to use to retrieve the correct DefinitionManager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TILES-115) MutableTilesContainer.register methods
should have a request parameters
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli closed TILES-115.
----------------------------------
> MutableTilesContainer.register methods should have a request parameters
> -----------------------------------------------------------------------
>
> Key: TILES-115
> URL: https://issues.apache.org/struts/browse/TILES-115
> Project: Tiles
> Issue Type: Improvement
> Components: tiles-api
> Affects Versions: 2.0.0
> Reporter: Antonio Petrelli
> Assigned To: Antonio Petrelli
> Fix For: 2.0.2
>
>
> Currently the MutableTilesContainer.register method has only a TileDefinition parameter, but a request parameters (the pair "request-response" or "PageContext") are necessary for two reasons:
> 1) In Tiles 1.x a custom definition lies in request context and to provide compatibility this should be its behaviour.
> 2) CachingKeyedDefinitionsFactoryTilesContainer stores a DefinitionManager for each key (calculated from a TilesRequestContext), therefore it cannot know which is the key to use to retrieve the correct DefinitionManager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TILES-115) MutableTilesContainer.register methods
should have a request parameters
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli updated TILES-115:
-----------------------------------
Affects Version/s: (was: 2.0.2)
2.0.0
Fix Version/s: (was: 2.0.x)
2.0.2
> MutableTilesContainer.register methods should have a request parameters
> -----------------------------------------------------------------------
>
> Key: TILES-115
> URL: https://issues.apache.org/struts/browse/TILES-115
> Project: Tiles
> Issue Type: Improvement
> Components: tiles-api
> Affects Versions: 2.0.0
> Reporter: Antonio Petrelli
> Assigned To: Antonio Petrelli
> Fix For: 2.0.2
>
>
> Currently the MutableTilesContainer.register method has only a TileDefinition parameter, but a request parameters (the pair "request-response" or "PageContext") are necessary for two reasons:
> 1) In Tiles 1.x a custom definition lies in request context and to provide compatibility this should be its behaviour.
> 2) CachingKeyedDefinitionsFactoryTilesContainer stores a DefinitionManager for each key (calculated from a TilesRequestContext), therefore it cannot know which is the key to use to retrieve the correct DefinitionManager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TILES-115) MutableTilesContainer.register methods
should have a request parameters
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli updated TILES-115:
-----------------------------------
Affects Version/s: (was: 2.0.0)
2.0.2
> MutableTilesContainer.register methods should have a request parameters
> -----------------------------------------------------------------------
>
> Key: TILES-115
> URL: https://issues.apache.org/struts/browse/TILES-115
> Project: Tiles
> Issue Type: Improvement
> Components: tiles-api
> Affects Versions: 2.0.0
> Reporter: Antonio Petrelli
> Assigned To: Antonio Petrelli
> Fix For: 2.0.2
>
>
> Currently the MutableTilesContainer.register method has only a TileDefinition parameter, but a request parameters (the pair "request-response" or "PageContext") are necessary for two reasons:
> 1) In Tiles 1.x a custom definition lies in request context and to provide compatibility this should be its behaviour.
> 2) CachingKeyedDefinitionsFactoryTilesContainer stores a DefinitionManager for each key (calculated from a TilesRequestContext), therefore it cannot know which is the key to use to retrieve the correct DefinitionManager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TILES-115) MutableTilesContainer.register should
have a "TilesRequestContext" parameter
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli reassigned TILES-115:
--------------------------------------
Assignee: Antonio Petrelli
> MutableTilesContainer.register should have a "TilesRequestContext" parameter
> ----------------------------------------------------------------------------
>
> Key: TILES-115
> URL: https://issues.apache.org/struts/browse/TILES-115
> Project: Tiles
> Issue Type: Improvement
> Components: tiles-api, tiles-core
> Affects Versions: 2.0.0
> Reporter: Antonio Petrelli
> Assigned To: Antonio Petrelli
> Fix For: 2.0.x
>
>
> Currently the MutableTilesContainer.register method has only a TileDefinition parameter, but a TilesRequestContext parameter is necessary for two reasons:
> 1) In Tiles 1.x a custom definition lies in request context and to provide compatibility this should be its behaviour.
> 2) CachingKeyedDefinitionsFactoryTilesContainer stores a DefinitionManager for each key (calculated from a TilesRequestContext), therefore it cannot know which is the key to use to retrieve the correct DefinitionManager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TILES-115) MutableTilesContainer.register methods
should have a request parameters
Posted by "Antonio Petrelli (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/TILES-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli resolved TILES-115.
------------------------------------
Resolution: Fixed
Split the "MutableTilesContainer.register" method in two, accepting also the "request/response" pair or the PageContext.
> MutableTilesContainer.register methods should have a request parameters
> -----------------------------------------------------------------------
>
> Key: TILES-115
> URL: https://issues.apache.org/struts/browse/TILES-115
> Project: Tiles
> Issue Type: Improvement
> Components: tiles-api
> Affects Versions: 2.0.0
> Reporter: Antonio Petrelli
> Assigned To: Antonio Petrelli
> Fix For: 2.0.x
>
>
> Currently the MutableTilesContainer.register method has only a TileDefinition parameter, but a request parameters (the pair "request-response" or "PageContext") are necessary for two reasons:
> 1) In Tiles 1.x a custom definition lies in request context and to provide compatibility this should be its behaviour.
> 2) CachingKeyedDefinitionsFactoryTilesContainer stores a DefinitionManager for each key (calculated from a TilesRequestContext), therefore it cannot know which is the key to use to retrieve the correct DefinitionManager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.