Tim Fox wrote:
>
> I'm interested in knowing people's strategies for deployment when
> developing a J2EE application. It seems impracticle (and time consuming)
> to me to have to repackage all the .war and .ear files and redeploy to
> the server everytime they make a minor change to an .htm, .jsp or .gif
> file during the development cycle.
Repackaging using the GUI tool is far too error-prone and time-consuming to be
done for every minor change. However repackaging using an automated process is
not too bad. The problem is that the GUI tool also creates the xml descriptor
files, so what I do is run the tool once simply to create compliant xml, then
extract the xml files from the generated jar files and save them. The I use a
command file to completely recreate the jar/war/ear files from the original
source and xml files.
Although programming with a text editor is very macho, it's a good idea to use a
good AD tool such as JBuilder which is capable of integrating with app servers.
This enables one-click compile and deploy to a version of the server running
under control of the AD tool and allows the programmer to bring the full range
of debugging techniques to bear in order to perform "unit tests".
When there are multiple developers working on different parts of a project we
also regularly regenerate everything completely using our automated build
process to create a "best so far" system that the "system testers" test against.
Ian McCallion
Alexis Systems Limited
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
