What is standard folder structure for an enterprise application using Spring, Hibernate, EJB, Web services


I want to start working on application using Java, J2ee, Spring, Hibernate, EJB, JUnit.
Can somebody tell me what could be the best folder structure to follow for an enterprise application where I'll be generating war, jar and ear.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It would depend upon what application layers you have. A normal best practice is to use the different layers as parent structures. You may choose a variation, where you use your modules as parent folders and then, use the layers.

For eg:-

<app root src>
      |---------------web       (spring/jsp)  
      ----------------entities (hibernate entities)
      ----------------process (session ejb stuff)
      ----------------utilities  (helper classes)
<app root test> (follow same structure as above and have junit tests for different layers)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java App Servers

From novice to tech pro — start learning today.