----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 20, 2002 1:25 PM Subject: Re: Web Service and EJB with Axis and JBoss
> > This sounds very similar to what I'm already doing (everything in > webapps/axis is being put into a .war file, and we are adding our own > service .jar files into the WEB-INF/lib directory so that Axis can find > them). > > We have the need to deploy Axis on a system, and then at random points in > the future, add new Axis services without shutting down JBoss or > re-deploying Axis itself. This would essentially mean dropping a new .jar > file on the system, and running the AdminClient. The problem is: how does > the Axis servlet know how to get at the newly deployed .jar file? It won't > be in the CLASSPATH when deployed on the system, and it won't be located > in the axis.war file. > > As far as adding axis.jar to each service when it gets deployed, I'm not > sure this will work. > > Have I misinterpreted your statement? ok, you are adding new servlets *with code* to a running web service. Interesting; I dont do that. I do a reload and redeploy, followed by a set of functional tests. Class files you add to a war files WEB-INF/classes should be automatically picked up; you need to test that, of course. The axis docs all indicate that adding new jars to WEB-INF/lib work too. However, I suspect that you will find that tomcat on jboss does do a webapp reload when it detects changed files; that is how tomcat behaves for any change in an expanded WAR file. This means that sessions may get broken. NB, I do like to be able to add and then take away endpoints on the fly; the only toolkit that makes this trivial (from your own code) that I have encountered is .NET remoting. (not ASP.net). -steve
