----- Original Message ----- From: "Stephen McConnell" <[EMAIL PROTECTED]>
Mucking around with the return type on the current lifecycle stage extension would not be an option as this is a released interface.
So we're tied to each released interface... Not sound particulary good as this limits evolving.
There is nothing stopping evolution. All I'm saying is that you can not change the return time on the existing lifecycle extension interface methods because that would break backward compatibility. It is clear the the approaches to container extension are open territory for evolution - just do it under a fortress scoped package name and you'll be safe.
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
