Apply only http://issues.apache.org/jira/secure/attachment/12340048/
GERONIMO-2163-v6c.patch
There are some instructions on setting up a testbed that require some
other files. Personally I wasn't able to follow all of them but I
think this patch is worth applying anyway.
The clustering contract is in the new module geronimo-clustering and
to the extent I understand (probably small) it it looks pretty self-
explanatory to me.
New modules:
geronimo-clustering: interfaces for proposed clustering contract
geronimo-clustering-wadi: implementation of this contract for WADI
geronimo-clustering-builder-wadi: a NamespaceDrivenBuilder to set the
aforementioned stuff up
Modified modules:
geronimo-deployment: improvements to NamespaceDrivenBuilder (requires
changes in all the NDBs, geronimo-service-builder and geronimo-
security-builder)
geronimo-jetty: changes to get jetty to talk to the clustering
interfaces as appropriate
geronimo-jetty-builder: changes to allow the wadi clustering builder
to be plugged in.
New Configs:
jetty-clustering-wadi: "static" support for wadi, sort of like the
jetty container.
jetty-clustering-builder-wadi: the jetty-wadi-builder
Modified Configs:
jetty: use the clustering interface
jetty-deployer: add the clustering builder if present
Modified assemblies:
geronimo-jetty-j2ee: include the new configs
Hope this helps
thanks
david jencks
On Sep 12, 2006, at 12:03 PM, Jeff Genender wrote:
Wow...that's a *lot* of patches. Before applying and giving a +1, can
we just get a small synopsis here on the clustering contract and
bullet
point of the contents. Also...which patch to apply? ;-)
Jeff
David Jencks wrote:
I'd like to thank the PMC members who promptly reviewed my jta 1.1
and
jndi refactoring patches and point them to an at least equally
deserving
patch that has been quietly mouldering for lack of attention
http://issues.apache.org/jira/browse/GERONIMO-2163
Aside from
- Integrating WADI in an architecturally appropriate way (finally!)
- Providing a clustering api as a basis for discussion and further
development
this also now includes a big improvement to the
NamespaceDrivenBuilder
interface that lets these builders add stuff to the environment. We
should be able to leverage this to e.g. only include axis when you
are
actually using a web service and/or switch webservices
implementations.
thanks
david jencks
