In principle I think this is a good idea. I'm not 100% sure the possible implementation complexity will be worth the gains...
1. You can already redeploy a subpackage of even a packed .ear by using the jmx console and MainDeployer.redeploy. You can do the same thing with the ant jmx task. Personally I think that using the ant jmx task to deploy/redeploy explicitly is more development-friendly tnan copying to a particular directory. In any case I highly recommend you try this out in various combinations to see what will work... 2. You may need a UnifiedClassLoader per class or to reload substantial parts of the application or be very careful about packaging. At the minimum you will have to keep ejb interfaces and implementations in separate packages so you don't have to reload the servlet clients. With the project I've played with "redeploy just a bit" with I haven't straightened out how to redeploy just the ejb implementations without the interfaces or depending packages. david jencks On 2002.10.02 13:38:01 -0400 "Gredler, Dani" wrote: > Hi, > > I'm thinking about adding some code to JBoss to provide better > granularity > to the [hot] deployment of directories. Here's the situation: I'm getting > tired of repackaging my EJB's into a JAR, creating a WAR, combining them > into an EAR, dropping the EAR file into the deployment directory, and > waiting for the whole EAR to redeploy before testing my one-line change. > > Now, I know JBoss lets you drop a directory in the hot-deploy directory, > and > as long as it matches the EAR file structure, it will deploy it, and I > have > considered using this. What I would like, however, is to be able to make > my > one-line change to one of the EJB's in the directory, recompile the > .class > file, and have JBoss automatically recognize that the one EJB in the > application needs to be redeployed, instead of having to redeploy the > whole > application. This would speed my development on JBoss incredibly, and > would > mitigate what I consider to be the Achilles heel of J2EE development. > > I've looked through the JBoss code available for download on the site, > and > from my quick perusing am inclined to think that, among others, my > changes > need to happen in: > > org.jboss.net.protocol.file.FileURLConnection - change the implementation > of > getLastModified() so that it recurses all subdirectories and checks all > files for modifications, not just the base directory. > > org.jboss.deployment.URLDeploymentScanner - change the implementation of > scan() so that modified directories do not get bluntly undeployed and > redeployed. Instead, intelligently determine which parts of the > application > need redeploying, and do them instead. > > Basically I'm looking for feedback here. Is there an easier way to > achieve > my goal than this? If not, am I on the right track as far as how to make > the > changes? Does anyone who is more familiar with the code than I have any > suggestions or pointers? > > Thanks for reading my long rambling post :) > > Dani > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
