> From: Leo Simons [mailto:[EMAIL PROTECTED]] > > There are several other areas that deserve focus as well, > like documentation and examples.
Yes, and those are things that need to be done now--with A4. > > Lastly, I would like to bring two more points to the table: > > * We should consider an additional lifecycle for a > persistence layer. > > I think if we want something like this it would be good to > take a look at the "custom marker proposal" (bad name) Marcus > is working on, and try and integrate. Yes, but a standard is also worthwhile. > > * reference implementation for a session object. This is > how stateful > > session beans (EJB spec) and servlets manage state in an otherwise > > stateless environment. It is also how they can manage to > be used by > > multiple threads or contexts of execution simultaneously. > We should > > put together a reference implentation of this in > excalibur and then > > vote whether it should be incorporated as part of > Framework (at least > > the defining interfaces). > > which raises another question: should we have optional > interfaces (ones a container doesn't really have to > recognize) in framework or not? Framework defined the minimum contracts between a component and the container. The Session object proposal is the key usability feature (that doesn't have to wait for A5) that will enable stateful threadsafe components with a minimum amount of intrusion on the part of the component developer and the client of the component. It is something that we need to take care of before we deprecate the release() method because what we are talking about here will obviate the need for a release() mechanism. Until that we have sessions in some form, we do need to be able to release components (pooled implementations). Currently it is *possible* to provide pooled implementations of components without a release() method, but the workarounds necessary to make it happen render it not a solution. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
