On Sun, 2002-08-18 at 23:25, Paul Hammant wrote: > Folks, > > Because the Mailets that JAMES uses (think servlets) can demand a > ComponentManager from the JAMES kernel, they are going to try to cast > things to Component. At the beginning of this year, we decided that > Component was on the way out and it is now deprecated. Unfortunately > nobody knew that JAMES was tied to CompManager, we all assummed that > JAMES could migrate. Because there is a slim possbility that its user > community has their own Mailets, we must support Componentized > Cornerstone comps for JAMES. > > Our question is do we.... > > a) Put back Component on the Cornerstone blocks, with a note that it > will go again another month.
-1 > > or > > b) create a branch in Cornerstone CVS that supports the old Component way. +1, except branching is probably not neccessary > > or > > c) find some clever wrapper way of supporting Componentized blocks. -0 my thoughts: cornerstone is a released product. Client API for the current revision should be similar to the released product. Client API for the next major revision should move away from using deprecated parts of avalon framework. It seems to me the right thing to do is to create a 1_1 tag on HEAD with the 'extends Component', then work on the HEAD branch without use of Component, then make sure the next tag of HEAD is 2_0 or higher and the next release is 2.0. cheers, Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
