beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zach Smith (JIRA)" <...@beehive.apache.org>
Subject [jira] Closed: (BEEHIVE-118) Improved semantic validation of @ControlExtension
Date Wed, 24 Aug 2005 20:04:09 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-118?page=all ]
     
Zach Smith closed BEEHIVE-118:
------------------------------


> Improved semantic validation of @ControlExtension
> -------------------------------------------------
>
>          Key: BEEHIVE-118
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-118
>      Project: Beehive
>         Type: Bug
>   Components: Controls
>     Versions: V1Beta
>     Reporter: James Song
>     Assignee: Kyle Marvin
>     Priority: Minor
>      Fix For: v1m1

>
> This originates from CR178618.
> Problem: when SubControl.java is declared like in the sample:
> @ControlExtension
> public interface SubControl extends ExtensibleControl
> {
>     ...
> }
> A runtime error occurs.
> The real issue here is that SubControl.java is a Control public interface (that extends
another Control Interface), but has the @ControlExtension annotation, when it really should
have the @ControlInterface annotation.
> The basic rule of thumb is that a JCX file has @ControlExtension, and generally has no
associated Impl (methods are handled by Extensible.invoke) on the associated Impl; more direct
impl subclassing (with associated interface extension) is done using the @ControlInterface.
> The checker should have detected this.

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


Mime
View raw message