You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> on 2007/06/24 15:42:55 UTC
[jira] Updated: (TAPESTRY-392) Way to specify default
implementations for @Beans
[ https://issues.apache.org/jira/browse/TAPESTRY-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-392:
-----------------------------------
Fix Version/s: (was: 4.1.2)
4.1.3
> Way to specify default implementations for @Beans
> -------------------------------------------------
>
> Key: TAPESTRY-392
> URL: https://issues.apache.org/jira/browse/TAPESTRY-392
> Project: Tapestry
> Issue Type: New Feature
> Components: Annotations
> Affects Versions: 4.0
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 4.1.3
>
>
> When attaching a @Bean annotation to a method whose return type is an interface, it is necessary to set the value attribute of the annotation to the class to be instantiated.
> It would be nice if there was a configuraiton point for mapping interfaces to implementation classes.
> This would allow
> @Bean
> public abstract IValidationDelegate getDelegate();
> To work, as long as we mapped IValidationDelegate to org.apache.tapestry.valid.ValidationDelegate somewhere.
> Of course, there needs to be the factory defaults / application overrides split as elsewhere.
--
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