Which is better ? Single EAR file or Multiple EAR files ?

For a single EAR file application, sometimes, only a small part of the application needs to be updated, then the whole application needs to be compiled and the whole EAR file needs to be installed.

Heard that we can split one EAR file into different EAR files. Has anyone tried that before ? Care to share your experiences on multiple EAR files ?

But how should I package the EAR files ? Put the common classes in one EAR file and the rest in another ?

So when I make changes to one EAR file, do I need to re-build the other one and re-install into the production server again ?

[605 byte] By [bronze-starDukes] at [2007-11-26 12:13:45]
# 1

Haven't tried multiple EAR files before but encountered constraints when using one EAR file.

For example, we may need to wait for another colleague to complete his portion on programming so that we can proceed to implement the entire EAR file. Is this also a constraint for multiple EAR files application ?

If we can separate the EAR files into different modules, different colleagues can work on different modules concurrently. It could be more efficient... Is that the case ?

bronzestar at 2007-7-7 14:15:25 > top of Java-index,Archived Forums,Socket Programming...