thanks, that does make more sense. I was following the lead of samples/userguide/example3/undeploy.wsdd which seems to be in error.
From: Glen Daniels [mailto:firstname.lastname@example.org]
Cc: 'email@example.com'; 'firstname.lastname@example.org'
Subject: RE: Undeploying services and handlers
(answer crossposted to axis-user and axis-dev - please restrict replies to axis-dev)
The problem here is in the undeploy.wsdd file - the top-level element should be <undeployment>, not <deployment>. So the problem you're seeing is a result of *deploying* "blank" handlers and services. This needs to get fixed so that we throw an appropriate fault. But if you change your element to <undeployment>, you should be able to undeploy this just fine.
The same problem holds with your earlier example of undeploying just the handler (i.e. you were actually deploying a blank copy of the handler, not undeploying it), except that if you undeploy the handler and not the service, the service will break. Long run, we should be reference counting this stuff so that you can't undeploy handlers that are being used by other chains/services, but for now the solution should be returning better error messages.
Thanks for using the package, and keep up the great feedback!
From: Chris Haddad [mailto:email@example.com]
Wednesday, December 05, 2001
Subject: Undeploying services and handlers
I didn't see my postings coming through on axis-dev, so I'm cross-posting this to the user's list.
When I run the following undeploy.wsdd file, the server-config.wsdd file is nulled out to a zero size, and the 'list' command throws and exception.
Is there a bug in my undeploy file?
Here's the undeploy.wsdd used to attempt removal of the handler and the service:
Note, when I just undeploy the service, LogTestService, and don't reference the handler, all is ok. Although, there is still a vestigial reference when performing the list command," <service name="LogTestService"/> "