beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chad Schoettger" <chad.schoett...@gmail.com>
Subject Re: @Control and BEEHIVE-1087
Date Fri, 31 Mar 2006 21:09:46 GMT
Hey Eddie,

I have some time to take look at this one.  I'll go ahead and start working
on a fix, assuming no one on the list has any issues with this change.

 - Chad

On 3/31/06, Eddie O'Neil <ekoneil@gmail.com> wrote:
>
> Jess--
>
>   Heh...that's a pretty interesting problem.  After looking at the
> repro, it seems like this is the case that doesn't work:
>
> src/
>   a/
>     FooControl.java
>     FooControlImpl.java
>   b/
>     FooControl.java
>     FooControlImpl.java
>   ControlClient.java
>
> where ControlClient has something like:
>
>   @Control
>   private FooControlBean _fooControl;
>
> If I understand this correctly, the problem is that the
> ControlClientAnnotationProcessor takes a best guess when it can't find
> an exact match for the name of the Control's interface type.
>
>   An "interfaceHint" attribute would allow the AP a chance to resolve
> the type if the type isn't otherwise available from the field's
> declaration.  The above example would then look something like:
>
>   @Control(interfaceHint=a.FooControl.class)
>   private FooControlBean _fooControl;
>
> This would give the AP an "out" (if you will) to handle cases like that
> above.
>
> I'm fine making this addition -- thoughts from anyone else?
>
> Eddie
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message