How would this help in the least? My understanding is that if you use a directory, the dd is checked for time changes and if it changes the whole app is undeployed and redeployed. Unless you can put your app in independently deployable chunks, you will need to undeploy and redeploy the entire application anyway.
Why can't you use the Scoped Classloader, which puts several ears into the same classloader and application? Also if the problem is with jsps I thought I saw somewhere that you could change the copied, deployed, unpacked jsp files while the app was running and they would get picked up and recompiled. Haven't tried this though. david jencks On 2001.11.21 03:58:06 -0500 Rickard �berg wrote: > Hey > > Developing with JBoss used to be very good due to hot deploy features. > Now that our app is growing rapidly (mostly LOADS of JSP's) we're seeing > that it's not so nice, because we have to package the app as an EAR file > before deployment. If JBoss could work from a directory, that would cut > down the dev cycle by a lot. > > Looking at the J2EE deployer it seems as though it can take a directory > as input. However, if that is the case, then it gets packaged into a JAR > anyway! Thus, the overhead we skipped by not packaging it into an EAR > file in the first place is added anyway. > > Is this really necessary, and would it be possible to change it? As it > is, we have a redeploy cycle of about a minute, which is not nice... > > /Rickard > > -- > Rickard �berg > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
