Note that there are some explanatory texts on larger screens.

plurals
  1. POLarge Enterprise Java Application - Modularization
    text
    copied!<p>I work for a country-wide company, so the software we develop is large scale.</p> <p>Our core system is Web based including <code>webservices</code>. We are currently redesigning the entire project and is moment to start the project structure.</p> <p>We have like 7 web modules including for the web project based on <code>Struts2</code> and <code>Spring 3.1</code>. A <code>Webservice</code> core based on <code>JAX-WS</code> and <code>Spring 3.1</code></p> <p><strong>My question is what are the best practices to design the project structure and modularization for a project like this:</strong></p> <p>We'll definitely use <code>Maven</code> and <code>OSGi</code> if needed. I'm thinking in something like</p> <pre><code>WebProject.war |---Web.xml |--- Libs | |--- Web Module1.jar |--- Web Module2.jar |--- Web Module3.jar |--- Web Module4.jar |--- Web Module5.jar |--- Web Module6.jar WebService.war |---Web.xml |--- Libs | |--- Service.jar |--- Service2.jar EJBProject.jar | |--- module.jar |--- module2.jar </code></pre> <p>This is what I personally have in mind, but we are looking for something better modularized so we can work and deploy <code>WebModule1.jar</code> without affecting the other modules and main project <code>WebProject.war</code>. Also with this we want the specialized teams to only have the code of their projects, so if a Team must work only with <code>Service2.jar</code> in their <code>IDE</code> they will only have the code for <code>Service2.jar</code> and a resource project with the others project already compiled.</p> <p>Thanks</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload