On 11/01/2008, at 7:15 AM, David Jencks wrote:
Could you update us on your guess for a time frame for the SFSB
clustering? Will this require OpenEJB changes? Is it realistic to
get this into 2.1?
Hello David,
I still target to complete SFSB clustering over the week-end. If this
is not the case, then it will definitively be completed next week-
end. This requires some OpenEJB changes: basically, a clustered
stateful container is added and some SFSB related classes are updated
to run passivation and activation logic when migrating SFSB instances
from one node to another one.
I believe that if a 2.1 branch is ready to be cut, then it should be
cut as soon as possible and not wait for the above stuff to be
completed. The above stuff can be shipped as part of a subsequent 2.2.
3. Jetty and tomcat now have some reliance on some base
clustering classes which are only available in the clustering
config. I think the base classes should be provided in e.g.
j2ee-server and things arranged so that if you don't have the
clustering config you don't get clustering, and if you do have it
you do get clustering. It might be that all the actual
clustering gbeans could go into wadi-clustering, I haven't looked
into this.
This is an approach.
What do you think of this approach - for Jetty?
* create a new project plugins/jetty/geronimo-jetty6-clustering;
* move the package org.apache.geronimo.jetty6.cluster to this new
project; and
* add a new dep. to jetty6-clustering-wadi.
This way, the jetty6 config does not depend on clustering.
I'll have to look at this more to understand it. If you think it
solves the problem, please go ahead.
I have checked in the above approach early this week while working on
a problem reported by Jarek. I think this solves the problem you
reported.
I will now move the farm related classes as suggested.
Thanks,
Gianny
thanks
david jencks
