Hi David,
Your post is opportunistic for me to raise some concerns on dual
configuration style, one via GBean and another one via the native
configuration mechanism, which may cause trouble to users.
No more than a couple of hours ago, I was trying to make sense of a
port conflict related to the ActiveMQ Broker trying to bind to the
same port whatever the value of PortOffSet. I figured out that I had
to change the port configuration in the activemq.xml configuration
file of the instance I was trying to start. The typical user
expectation is that PortOffset should be honored whatever the
configuration style.
I do not have a solution; though I wanted to report on this bad
experience.
Thanks,
Gianny
Begin forwarded message:
From: David Jencks <[email protected]>
Date: 14 January 2009 7:18:59 PM
To: [email protected]
Subject: Re: Add tomcat-specific configuration
Reply-To: [email protected]
On Jan 13, 2009, at 8:32 PM, Ivan wrote:
I was always thinking that shall we have a better way to handle
all the available setting provided by the third-party modules? As
we all know, usually, all the GBeans only delegate those important
and popular settings, it is impossible for us to allow all the
configurations could be done via GBean. Let us take Tomcat as an
example, maybe we shall give an interface to set those
configurations that we do not provide now.
I think we could expose all the knobs on tomcat components in our
gbeans but it might not be the most usable approach. Basically the
problem is that we have two component containers -- tomcat and
geronimo -- both of which insist on creating all the components
themselves. While I tend to think that the main problem is that
tomcat mixes the lifecycle and runtime code to intimately the only
realistic way to get farther than we have now is to change geronimo
so the components don't have to be created directly by the gbean
infrastructure.
david jencks
2009/1/14 Jack Cai <[email protected]>
Thanks Ivan! I've examined the geronimo-tomcat-2.0.1.xsd and
geronimo-tomcat-config-1.0.xsd, and am pretty sure many
configurations are not available, like antiJARLocking,
unloadDelay, etc. I understand that many of these settings might
not work in Geronimo. Just try to see how we can play with the
context.xml etc., which might be some good tips for migration from
Tomcat.
-Jack
2009/1/14 Ivan <[email protected]>
Basically, Geronimo have created a GBean for each element in the
server.xml, which means we should configure those settings via
GBeans in the config.xml. But so far, I am sure the existing
GBeans have not covered all the settings that tomcat provides.
e.g. for server.xml, we have host gbean for the <HOST> element,
actually, you could check the current setting in the geronimo
\plugins\tomcat\tomcat6\src\main\plan\plan.xml. For the
context.xml, a TomcatWebAppContext GBean will be created while
deploying the web applications, and most configurations could be
set in the geronimo-web.xml file.
Thanks for any comment, if any mistake is made, please point it out !
2009/1/13 Jack Cai <[email protected]>
I just realize that I can put a context.xml in var/catalina/conf
so that I can specify lots of Tomcat options there. I did a small
experiment with the "workDir" param and it seems taking effect.
Wondering whether this is supposed to work? Can I also put a
server.xml there? Thanks!
- Jack
--
Ivan
--
Ivan
