[
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.
