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

Posted to dev@beehive.apache.org by "Kenneth Tam (JIRA)" <be...@incubator.apache.org> on 2005/02/23 03:13:50 UTC

[jira] Updated: (BEEHIVE-135) Version checking codegen cleanup

     [ http://issues.apache.org/jira/browse/BEEHIVE-135?page=history ]

Kenneth Tam updated BEEHIVE-135:
--------------------------------

    Fix Version: V1
                     (was: V1Alpha)

> Version checking codegen cleanup
> --------------------------------
>
>          Key: BEEHIVE-135
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-135
>      Project: Beehive
>         Type: Bug
>   Components: Controls
>     Versions: V1Alpha
>     Reporter: Kyle Marvin
>     Assignee: Kenneth Tam
>     Priority: Minor
>      Fix For: V1

>
> The code generated static initialization code that does version checking for ControlBeans could be made better in a couple of ways:
> - the code generated by the enforceVersionRequired macro should be selectively generated.   There is no reason to generate class load time version checking if there is no @VersionRequired annotation on the associated ControlExtension.
> - the ControlInterface to version check against can be (and should) be determined at codegen time and not runtime.   The call to ControlBean.getMostDerivedInterface can be replaced by directly injecting the (versioned) ControlInterface class name.  This is a) simpler, and b) safer, because having the class you are version checking against be dynamic doesn't really make sense.

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