Would it be considered bad practice to bundle a small Java EE app with EJB's in one war file?

Question

I am working on a small Java EE application which also uses EJB's. It is a very small application with just a few beans.

Right now I am bundling the entire application in one war file. Would this be considered bad practice ? Should I create another project and resulting jar file for the EJB's ?

From a practical view point (besides being able to reuse the EJB's in multiple projects), what are the pros and cons of deploying everything in one war file vs. splitting them into war + jar files ?

also see http://stackoverflow.com/questions/6785924/jar-packaging-and-distribution — shinynewbike, Apr 16 '12 at 11:06

score 2 · Answer 1 · edited May 23 '17 at 12:27

2

To respect the Java Multitiered architecture it's better to keep the EJB in a JAR. It's a better practice to separate the business logic from the Web tier. Then you can use EAR (check this too) for deployment. But if your application is small and will not grow up it's acceptable to put everything in a War.

edited May 23 '17 at 12:27

Community

1
1

answered Apr 16 '12 at 09:41

alain.janinm

19,951
10
65
112

Would it be considered bad practice to bundle a small Java EE app with EJB's in one war file?

1 Answers1