The idea seems OK. I saw that you fixed section 4.2 too, so as to
preserve inheritance of producer and observer methods through
specialization, which was my initial concern when I read your proposal.
I'd move section 5.2.3 ("Inconsistent specialization") back under 4.3,
by the way.
I also noticed that 5.2.2 reads like a riddle. Maybe it'd work better if
it was stated in terms of what it means to be "disabled".
Gavin King wrote:
I'm still waiting for feedback on this proposal. If I don't
hear
anything, I'm going to assume that silence indicates consent!
Not that this is a functional change to specialization.
On Wed, Aug 26, 2009 at 7:49 PM, Gavin King<gavin.king(a)gmail.com> wrote:
> I've been discussing the following change with Pete:
>
> Currently, the spec says that when a bean X is specialized by some
> enabled bean Y, X is still considered enabled, and its producer
> methods are also enabled, but they get called on Y instead of X.
>
> However, the following is simpler to implement, specify, and probably
> understand:
>
> When a bean X is specialized by an enabled bean Y, X and all its
> producer methods are considered disabled.
>
> This definition lets us get rid of the whole notion of "most
> specialized enabled bean".
>
> I'm attaching a spec which incorporates the necessary changes, mainly
> in 4.3 and 5.2.
>
> WDYT?
>
> --
> Gavin King
> gavin.king(a)gmail.com
>
http://in.relation.to/Bloggers/Gavin
>
http://hibernate.org
>
http://seamframework.org
>
>