Generally you can redeploy subpackages inside and .ear: this is pretty easy to do when the .ear is deployed "exploded" (you have a directory named mystuff.ear, and the contents are inside), and I have also done this by modifying the contents of the .ear using emacs and redeploying a subpackage explicitly using MainDeployer.
However, there are big limits on what is possible, especially with utility classes. If you have package A using classes from package B, and something from A has an actual reference to a class from package B, you may be able to redeploy B without apparently redeploying A, but nothing will work: you may have 2 differenct versions of the classes from B. To fix it, you have to redeploy A also. Sometimes you can sort of work around this, especially with ejbs. If you separate all the interfaces into a package separate from the implementation, you may be able to redeploy the implementation classes without redeploying the interfaces. david jencks On 2002.12.14 21:45:24 -0500 Jee-Meng Ang wrote: > Looks like we need to do some more experiments. I am not actually > concerned > about hot deployment of EJB-JARs, WARs and EARs as we all know it works. > > However I have now come to a sticky situation whereby I need to build > least > common denominator strategy for packaging my classes for deploying across > multiple App Servers namely JBoss (of course), WebSphere and Weblogic. > The > other way of course to configure ANT to have several targets to different > App Servers but this will be a pain to maintain. > > In any case I have built a library of classes that is common to most web > applications. These classes are packaged into separate JARs and commonly > deployed to all my web applications on different App Servers. > > Having common JARs has several advantages in terms of version control and > testing common and "framework" classes as they have already proven to be > working correctly and does not change very often. However there are > cases > where some application breaks those components and work has to be done to > fix it and retest across all applications before redeploying them. > > In JBoss, I have yet to find out that this strategy works and whether > common > JARs can be hot deployed. > > As far as I know JBoss 2.x's deployer can reference non-EJB jars within > the > deploy directory during hot deployment. Any classes not found within the > EJB or WAR package can reference to the common JARs and the deployer will > be > happy and does not complain about any missing classes. > > However after deployment the EJBs and classes in the WAR packages could > not > reference the classes in the common JARs. > > This is why I posted my initial message to find out whether JBoss users > out > there having the same problems. > > JM > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of John Fawcett > Sent: Sunday, December 15, 2002 4:14 AM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] EAR, EJB-JAR, and WAR with Dependant JARs > > > I think you can deploy an uncompressed ear as a directory. Then you can > just > deploy the constituent jar/war files into that directory. So you can hot > deploy the individual jars/wars, rather than the whole ear. > > nb: I haven't tried this myself, but the jboss-net sar is uncompressed in > jboss-head and works fine. > > good luck, > fawce > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Jee-Meng Ang > Sent: Saturday, December 14, 2002 1:59 AM > To: JBoss-User (SF) Mailing List > Subject: [JBoss-user] EAR, EJB-JAR, and WAR with Dependant JARs > > > I have a question regarding the deployment of dependant JARs. According > to > J2EE spec, EJB-JARs and WAR are able to refer to another JAR in the same > EAR > using the Class-Path property within the MANIFEST.MF files. > > But using EARs for deployment means that the development-deploy-test > cycle > take a long time due to the overhead in packaging and redeploying the > EAR. > This will discourage developers from doing incremental development. > > JBoss supports hot deploy of individual EJB-JARs and WARs. Who can live > without this feature. However, can JBoss support reference of classes in > other Jars from EJB-JARs and WARs through MANIFEST.MF? If so, where > should > I deploy these dependant Jars? And can the Jars be hot deployed just > like > the EJB-JARs and WARs? > > Any help and pointers will be deeply appreciated. > > Regards, > Jee-Meng Ang > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
