> Leo:
hi! Thanks for the feedback ;)
>
> Have been browsing around inside the proposal src tree of Avalon
> and Phoenix
> in an attempt to locate an interface against which a
> LifecycleConflictException could be thrown - i.e. an exception
> that refused
> to do something based on the grounds that the object does not support the
> necessary set of required interface patterns (i.e. to suspend one must be
> able to resume). Not knowing the code all that well - I haven't
> locating an
> appropriate target - perhaps someone else knows where I should be looking.
It is nonexistent. I don't think this needs to be in 4.0 - we'll
make it the responsibility of the parent object for now to check
for this (by contract, not interface).
> In the meantime, I did take a look at the Embeddor interface in
> org.apache.phoenix.core. I think this should be modified to include
> Stoppable in the inheritance path of the interface because it currently
> includes Disposable and according to the limited documentation on
> Disposable, the dispose operation can only be disposed of following the
> stopping of the class - i.e. it is implied that Embeddor is Stoppable by
> that fact that it is Disposable. If this is incorrect then the
> documentation for Disposable is out-of-date.
It is; there are more of these issues (like in some places it still
says configure() should be called before contextualize()). Many
services do not need to be stopped before they're disposed, so your
proposed change is also conceptually incorrect (which is probably
why it was made the other way in the first place).
cheers!
LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
