> I actually tried to do this for Avalon/Phoenix and could not figure out a
> nice way to do it at all.
=) Me neither. Exceptions are a language feature; to implement
a mechanism that offers the same functionality and clarity, and
satisfies IOC would require a language feature as well.
If you define exceptions as the one callback mechanism allowed
in the component framework, it may not be pretty but it does
provide some useful functionality.
Moreover, as exceptions are a language-level feature, it is all
but impossible to disable them. How about RMI-enable components?
Avalon might indeed benefit from adapting the Strategy pattern
in some cases, but again in agreement with TOL (The Other Leo),
this is not a pattern we should apply to (let alone require for)
the entire framework.
cheers,
LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
