what is the common practice to deploy a fix in J2EE

Thread view:

s o - 09 Aug 2006 18:39 GMT

Hi all,

let's say my web app has 10 modules and I created 10 jars(one jar for
each module) instead of 1 big jar; and the JSP's are subdivided into 10
folders. Initially, the app is deployed as one war file. Later, when
it's time to apply a fix that affects only one of the jars and one of
the JSP's, do you war everything and redeploy it or do you simply
replace that one jar and JSP? what is the common/best practice?
thanks.

s o

Reply to this Message

josh.s17@gmail.com - 09 Aug 2006 22:26 GMT

The safe way would be to deploy the whole WAR. Especially if you have
an automated build process which tags your repository when you build a
WAR.

However with some app servers (eg Tomcat you could probably get by
deploying just the jar).

> Hi all,
>
[quoted text clipped - 7 lines]
>
> s o

Reply to this Message

Mike Schilling - 10 Aug 2006 01:58 GMT

> The safe way would be to deploy the whole WAR. Especially if you have
> an automated build process which tags your repository when you build a
> WAR.
>
> However with some app servers (eg Tomcat you could probably get by
> deploying just the jar).

That wouldn't be safe, though. If the directory containing the exploded app
is ever deleted, Tomcat will re-expand the war and lose your fix.

Reply to this Message

Andrea Desole - 10 Aug 2006 08:56 GMT

> Hi all,
>
[quoted text clipped - 7 lines]
>
> s o

The solution of replacing small parts of an application are preferable
when it's more practical, for example when the application is very big
and you have to download it. This is not normally the case of a web
application. I would go for the war, it's the safer bet.

Reply to this Message

what is the common practice to deploy a fix in J2EE

Free Magazines