Berin, Agree, but can we pend this discussion until we finalise the GenericBlockConext one...
- Paul >>From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] >> >>Lifecycle Extensions >>---------------------- >>Controversial, there is no immediate need to expose them to *all* >>containers. >>We should though define that any Container that implements >>extensions is >>highly recommended to use the standard extension mechanism. >> >> > >Regarding this subject, my thinking on the subject is this: > >1) Containers need to declare if they support extentions or not. > If they do not, then any components requiring extensions are > not compatible with your container and the container must > refuse to load and use the components. > >2) Containers that DO declare that they support extensions must > support the common meta-model, and common interfaces. That supports > write-once, use many on the containers that do support extensions. > >3) Extensions must be verifyable--i.e. the handler must exist, > and the contracts must be obeyed. If not, then the container > throws an error message and the component cannot be used. > >Thoughts? > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
