[TAP5-529] Attach an annotation marker(s) with @Component to remove ambiguities of injection within a component.

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.1.0.0, 5.0.18
• Fix Version/s: 5.2
• Component/s: tapestry-core
• Assignee: Unassigned
• Reporter: Yunhua Sang
• Created: 19/Feb/09 21:16
• Updated: 27/May/14 12:34
• Resolved: 27/May/14 12:28

Description

Sometimes a component doesn't know which instance of a common interface is going to be used at design time; the appropriate instance of a common interface will be injected at runtime. For example, a JDBCTable component is using a DataSource:

public class JDBCTable {
@Inject
private DataSource dataSource;

@Parameter(required = true, defaultPrefix = "literal")
private String table;
....
}

When there are multiple DataSource existing, it seems hard to inject a DataSource I wanted into this component, a possible way is to make dataSource a parameter.

It would be nice that Tapestry 5 can remove this kind of ambiguities of injection by attaching an annotation marker(s) with @Component, as

@Oracle
@Component
private JDBCTable jdbcTable;

The @Oracle should has higher priority than the one(s) already defined in the component.