You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Alejandro Ramirez (JIRA)" <de...@beehive.apache.org> on 2006/04/29 00:24:38 UTC

[jira] Closed: (BEEHIVE-996) Compilation error on an extended control bean when callback intf on base ctrl intf and extended crtl intf have same name

     [ http://issues.apache.org/jira/browse/BEEHIVE-996?page=all ]
     
Alejandro Ramirez closed BEEHIVE-996:
-------------------------------------

    Assign To:     (was: Jacob Danner)

(Visible to beehive-developers)


> 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

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