David Jencks wrote:
It is possible (I think) to do what you want, but I do not recommend
it. I would prefer that you use external plans, and write 2 new
modules inside configs, to deploy your sample to jetty and to
tomcat. Take the geronimo-web.xml out of the app and put it in src/
Aaron Mulder wrote:
Well... is it possible to make this not specific to WADI? Perhaps
make it a generic clustering manager tag, and is just so happens
that the only classes we let you configure so far are the WADI ones?
Ideally, we'd put some generic interface in the Geronimo space, and
After further thought...
I imagine it going like this:
container checks for the WEB-INF/web.xml/distributable/ tag.
If it exists, container looks at the e.g.
geronimo-web.xml/distributable-session-manager/ tag.
The value of this tag could be either an enum (e.g. {WADI,...}), a
classname or
Aaron Mulder wrote:
Well... is it possible to make this not specific to WADI? Perhaps
make it a generic clustering manager tag, and is just so happens
that the only classes we let you configure so far are the WADI ones?
Ideally, we'd put some generic interface in the Geronimo space, and
Greg Wilkins wrote:
Aaron Mulder wrote:
Well... is it possible to make this not specific to WADI? Perhaps
make it a generic clustering manager tag, and is just so happens
that the only classes we let you configure so far are the WADI ones?
Ideally, we'd put some generic interface in the
Greg Wilkins wrote:
Aaron Mulder wrote:
Well... is it possible to make this not specific to WADI? Perhaps
make it a generic clustering manager tag, and is just so happens
that the only classes we let you configure so far are the WADI ones?
Ideally, we'd put some generic interface in the
In my personal experience, any machine in a cluster is fully in a
cluster -- I haven't seen something like 10 machines running 1
clustered app and then each running something else on the side.
However, it is kind of nice in WebLogic that you can deploy to either
a cluster or a single machine. I
Aaron Mulder wrote:
In my personal experience, any machine in a cluster is fully in a
cluster -- I haven't seen something like 10 machines running 1
clustered app and then each running something else on the side.
I can't agree...I may want to cluster my app, but I surely do not want
to
Aaron, David, or anyone in the know :-)
Maybe you can help me with this:
I have a WADI demo webapp.
To get it running with Jetty, I need a WEB-INF/geronimo-web.xml that
looks like this:
web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web/jetty-1.0;
configId=wadi
It is possible (I think) to do what you want, but I do not recommend
it. I would prefer that you use external plans, and write 2 new
modules inside configs, to deploy your sample to jetty and to
tomcat. Take the geronimo-web.xml out of the app and put it in src/
plan/plan.xml.
However,
Yeah, I was going to say, let's merge the manager and session-manager
elements from the 2 separate plans into a single session-manager
element in the geronimo-web plan. Though it looks like one takes a
class name and the other takes a GBean name, so we'd have to figure
that out. I assume that
Well... is it possible to make this not specific to WADI? Perhaps
make it a generic clustering manager tag, and is just so happens
that the only classes we let you configure so far are the WADI ones?
Ideally, we'd put some generic interface in the Geronimo space, and
then the WADI ones would
David J,
I thought when you added the separate Tomcat and Jetty namespaces, you
were going to remove the container-config section from the generic
geronimo-web.xml, but it seems that it's still there. Jeff thinks
maybe it's for something like the console, where we want it to work in
both Tomcat
13 matches
Mail list logo
