|
Hi, Is anyone else finding the Axis2 deployment model too
restrictive? I am running to issues with both a lack of a programmatic
API to deal with deployment and the inability to purge a service from a running
system. First, the only official way of deploying/managing services I
see is via the web interface. Why isn’t there an API and has anyone
figured out a way around this? Writing a servlet that lives in the same web
application as the Axis2 servlet does get you access to the Axis Configuration
object, but this is a hack. I saw a summer intern was working on a
JMX-based project to do Axis2 deployment, but we can’t bet our business
on such a project. Also, there seems to be a fundamental issue with deployment,
which is that once you drop a .aar file in a directory, it cannot be removed
while the servlet container is running, because of open file descriptors.
Thus, while the notion of activated and “inactivated” services was
recently introduced, this is transient behavior and the service springs back to
life when the container is restarted. For this to be used in a production
quality system there needs to be a definitive way to totally purge a service
while the system is up and running. Any feedback or suggestions are welcome. Thanks. Gary Gordon |
