You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@beehive.apache.org by "Kyle Marvin (JIRA)" <be...@incubator.apache.org> on 2005/02/25 04:04:50 UTC

[jira] Commented: (BEEHIVE-357) Limit type of annotations that can be externally overriden

     [ http://issues.apache.org/jira/browse/BEEHIVE-357?page=comments#action_59741 ]
     
Kyle Marvin commented on BEEHIVE-357:
-------------------------------------

I generally agree, but would include 'Class' in the list of interesting and useful things to configure externally.   Having a configurable binding model for interface->impl actually relies upon this.


> Limit type of annotations that can be externally overriden
> ----------------------------------------------------------
>
>          Key: BEEHIVE-357
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-357
>      Project: Beehive
>         Type: Improvement
>   Components: Controls
>     Versions: V1Alpha
>     Reporter: David Read
>     Assignee: Mike Foster
>     Priority: Minor
>      Fix For: V1

>
> JSR175 constrains the set of Java types that can exist as members (methods return type) on an annotation.  Some of those types don't really make sense for external configuration (e.g. Class or byte and arrays of Class or byte).  There's also a practical matter of allowing arrays of primitive types and nested annotations.  In those cases, the structural representation and any tooling should probably be in sync to make it easy to visualize what's being configured relative to the structure of the application.  There's also the complexity of defining what it means to change an array?  The simplest model would probably be a full replacement of the array, rather than specifying "changes".
> For v1, we should consider limiting annotations that can be overriden externally to those than contain only simple primitive types (e.g. String, int, float, boolean ... no arrays, no nesting).  The annotation processor for controls would have to enforce this so the user wouldn't see a downstream build error that could have been caught sooner.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira