You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/09/17 18:07:44 UTC
[jira] Closed: (TAPESTRY-2395) Configuration, OrderedConfiguration,
MappedConfiguration should all allow a Class to be contributed, rather than
an instance
[ https://issues.apache.org/jira/browse/TAPESTRY-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2395.
------------------------------------------
Resolution: Duplicate
Fix Version/s: (was: 5.1)
Assignee: Howard M. Lewis Ship
TAPESTRY-2678
> Configuration, OrderedConfiguration, MappedConfiguration should all allow a Class to be contributed, rather than an instance
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2395
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2395
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0.11
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> So there would be an override of the add() method that accepted Class<T> rather than T. Tapestry would autobuild an instance from the contributed class. The only tricky part would be if the type of the configuration really was Class.
> An additional variation when contributing a class would be for Tapestry to auto-assign a name for the contribution (this would be for OrderedConfiguration) based on the simple name of the class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org