axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels" <>
Subject Re: cvs commit: xml-axis/java/src/org/apache/axis/utils
Date Fri, 29 Jun 2001 12:10:43 GMT
That's what it means, for right now.  This is easily changed - it's meant to
be an intermediate step on the way to understanding what the engine should
really do.  For now if we want, we can have it write out server-config.xml /
client-config.xml after each change (i.e. after each Admin.process()), and
assume a single config file per server/client, in whatever the current
directory happens to be.  That's about 5 minutes of work.

Longer term, I'd like to have the ability to scope deployment (at least on
the server) in some way - i.e. be able to cleanly deploy and undeploy a
named "package" of stuff.  If everything sits in one big registry, that's
hard.  We can imagine a hierarchy like this:

AXIS_ROOT/engine-config.xml (global engine config)

So when Axis comes up (or gets kicked), it would know to load all the
services/*/engine-config.xml files under its root dir.  Again, this heads in
the WSDD direction where a deployment can contain all kinds of stuff, but is
packaged under a name.

You might also deploy a service packaged like the following:

  WEB-INF/ (??)

...dropping this into a "deploy" directory under AXIS_ROOT might
automatically expand the jar into a hierarchy under services/ via an


----- Original Message -----
From: "Doug Davis" <>
To: <>
Sent: Friday, June 29, 2001 6:34 AM
Subject: Re: cvs commit: xml-axis/java/src/org/apache/axis/utils

> Glen wrote:
> >I removed the engine's ability to save its registries to persistent
> storage
> >itself.  So to save an active configuration, you should do something
> >java org.apache.client.AdminClient list > engine-config.xml
> >(I changed the printing of "Doing a list" to go to stderr so this works)
> Can you elaborate on this?  Does this mean that if I deploy a service
> at runtime and then bring the server down and back up that the service
> will *not* be deployed?
> -Dug

View raw message