axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Davis" <>
Subject Re: Undeployment
Date Sat, 01 Dec 2001 12:52:29 GMT
I assume it was an oversight, but don't forget about
undeploying transports too.  And I'd go for undeploying
global config's - setting them to something empty isn't
as intuitive (although making it empty will have the same

"Glen Daniels" <> on 11/30/2001 04:51:40 PM

Please respond to

To:   <>
Subject:  Undeployment

I'm in the midst of implementing undeployment, and here's a quick summary
my current plans.

1) Make a separate <undeployment> element which can also be the top level
a WSDD document that gets deployed into an engine via the AdminClient.

2) <undeployment> allows children <handler>, <service>, <typeMapping>,
<chain>.  (should we allow <globalConfiguration> to be undeployed, or just
state that you deploy an empty one if you want that?)

3) Any attributes other than "name" on those children (except for
<typeMapping>, which allows "qname" and "languageSpecificType") will be

4) An undeployment will be processed in lexical order, which allows us to
think about reference counting later.  In other words, you shouldn't be
to undeploy a Handler until all references to that Handler (in chains,
services, etc) have themselves been undeployed.

Thoughts?  Potential issues?


View raw message