[ 
http://issues.apache.org/jira/browse/BEEHIVE-179?page=comments#action_57796 ]
     
Lawrence Jones commented on BEEHIVE-179:
----------------------------------------

You may not have a choice. As we go forward there are going to be sets of 
standard annotations which a custom control author may wish to use but which 
are not defined with PropertySet on them.

In this particular case the TypesJarName is something that is intrinsic to the 
development of the Service Control - if you want to change it you will probably 
at the same time need to change the source code of the JCX.

I don't want anyone who is not the JCX developer to be capable of changing 
this. Specifically I don't want authors of the control client or administrators 
to be able to set this property by calling setters.

> context.getControlPropertySet() should return null for non-existent annotation
> ------------------------------------------------------------------------------
>
>          Key: BEEHIVE-179
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-179
>      Project: Beehive
>         Type: Bug
>   Components: Controls
>     Versions: V1Beta
>  Environment: Windows
>     Reporter: Lawrence Jones
>     Assignee: Kyle Marvin
>     Priority: Critical

>
> I call
> ServiceControl.TypesJarName typesJarNameAnn =
>                 (ServiceControl.TypesJarName)context.
>                     getControlPropertySet(ServiceControl.TypesJarName.class);
> in the Impl of my control (ServiceControl). TypesJarName is a valid 
> annotation which is defined in the public interface  but not used in either 
> the public interface nor in the JCX.
> I expected to receive null but instead I get a non-null object with defaulted 
> values for its members.
> This is at odds with the javadoc for the API 
> ControlBeanContext.getControlPropertySet() and in any case you need a way to 
> be able to tell whether an annotation is present or not (especially if you 
> have marker annotations).

-- 
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

Reply via email to