The chart is only showing geronimo.import(parent) relationships and not
geronimo.dependency relationships (which would really make the diagram
cluttered and difficult to follow).
However, I checked and console-jetty doesn't include a
geronimo.dependency on jetty either. I believe that it isn't the
content of the configuration itself that makes it specific to jetty but
rather the deployment (using the jetty-deployer rather than the
tomcat-deployer) that makes it a requirement to have both jetty and
tomcat configurations of each application we pre-deploy.
Joe
Dain Sundstrom wrote:
This is a bit confusing. How can I have a console-jetty without a
dependency on jetty?
-dain
On Feb 27, 2006, at 6:36 PM, Joe Bohn wrote:
Here's an updated version of the chart (including the "duplicate"
dependencies that I had proposed removing but which are not yet
removed).
Joe
Joe Bohn wrote:
I'm not sure if these charts are helpful for anybody else or not.
It's a point in time snapshot that I created of parent (import)
dependencies between configurations at the moment (which some of the
changes that I have pending to clean up some dependencies).
The first page has the server configuration imports and the second
page includes the client and "childless" configs (configs not
referenced as parents by any other configuration).
If you think it's useful then I will try to find a location where we
can keep this ... but I suspect it would get out of date fairly
quickly.
Joe
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
<geronimo-config-parents.ppt>
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
