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/05/04 16:26:42 UTC
[jira] Updated: (TILES-87) BasicTilesContainer.calculateType is
called even if an attribute does not need preprocessing
[ https://issues.apache.org/struts/browse/TILES-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli updated TILES-87:
----------------------------------
Description:
The BasicTilesContainer.calculateType method is called for every attribute, even those that have been already preprocessed.
Therefore there is a (pretty small) performance problem. Currently is a case of a null check and a String comparison (plus a call, obiously), but in the future it could be more complex.
was:
The AttributeTag.calculateType method is called for every attribute, even those that have been already preprocessed.
Therefore there is a (pretty small) performance problem. Currently is a case of a null check and a String comparison (plus a call, obiously), but in the future it could be more complex.
Summary: BasicTilesContainer.calculateType is called even if an attribute does not need preprocessing (was: AttributeTag.calculateType is called even if an attribute does not need preprocessing)
Modified the issue with the changes in the code: now the "calculateType" method is in BasicTilesContainer.
> BasicTilesContainer.calculateType is called even if an attribute does not need preprocessing
> --------------------------------------------------------------------------------------------
>
> Key: TILES-87
> URL: https://issues.apache.org/struts/browse/TILES-87
> Project: Tiles
> Issue Type: Improvement
> Components: tiles-core
> Affects Versions: 2.0.0
> Environment: N/A (it's a design issue)
> Reporter: Antonio Petrelli
> Priority: Minor
> Fix For: 2.0.x
>
>
> The BasicTilesContainer.calculateType method is called for every attribute, even those that have been already preprocessed.
> Therefore there is a (pretty small) performance problem. Currently is a case of a null check and a String comparison (plus a call, obiously), but in the future it could be more complex.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.