beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie O'Neil (JIRA)" <...@beehive.apache.org>
Subject [jira] Assigned: (BEEHIVE-996) Compilation error on an extended control bean when callback intf on base ctrl intf and extended crtl intf have same name
Date Fri, 03 Mar 2006 03:38:43 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-996?page=all ]

Eddie O'Neil reassigned BEEHIVE-996:
------------------------------------

    Assign To: Eddie O'Neil

> Compilation error on an extended control bean when callback intf on base ctrl intf and
extended crtl intf have same name
> ------------------------------------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-996
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-996
>      Project: Beehive
>         Type: Bug
>   Components: Controls
>     Versions: V1
>  Environment: Win XP
>     Reporter: Pradeep Bollineni
>     Assignee: Eddie O'Neil

>
> The control bean generated for the control extension has ambiguous reference to Callback
interface in the callback listener methods when there is a callback interface extension in
the control extension as shown below:
> @ControlInterface
> interface BaseControl {
>     @EventSet
>     public interface Callback {
>         void method1();
>     }
> }
> @ControlExtension
> interface ExtendedControl extends BaseControl {
>     @EventSet 
>     public interface Callback extends BaseControl.Callback {
>          void method2();
>     }
> }
> Generated ControlBean listener method:
> public class ExtendedControlBean extends BaseControlBean implements ExtendedControl {
>     public synchronized void removeCallbackListener(Callback listener)
>     {
>         CallbackNotifier notifier = (CallbackNotifier)getEventNotifier(Callback.class);
//ambiguous reference as there is a Callback in BaseControlBean and ExtendedControl
>         notifier.removeListener(listener);
>     }
> }
> Is there a work around for this other than re-naming the interface in the extended control?

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