[ http://issues.apache.org/jira/browse/BEEHIVE-929?page=all ]
Rich Feit reassigned BEEHIVE-929:
---------------------------------
Assign To: Rich Feit
> Compiler check for base type agreement between the type and typeHint
> attributes of an action output annotation
> --------------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-929
> URL: http://issues.apache.org/jira/browse/BEEHIVE-929
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: TBD
> Reporter: Troy Beecroft
> Assignee: Rich Feit
> Priority: Minor
>
> Tools can use the typeHint attribute on an action output annotation to
> preserve information about parameterized types. Such tools might jointly
> manage both the type and typeHint attribute to keep them in synch. Even so,
> someone could change one and not the other either directly in source or via a
> property sheet. In such cases it would be really handy if there was a
> compiler check to see that both attributes have the same base type.
> As an example, the following annotation would pass:
> @Jpf.ActionOutput(name="customers", type=java.util.ArrayList.class,
> typeHint="java.util.ArrayList<businessObjects.Customer>
> while this one would not:
> @Jpf.ActionOutput(name="customers", type=java.util.ArrayList.class,
> typeHint="java.util.List<businessObjects.Customer>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
