Answer the question
In order to leave comments, you need to log in
Modularization of a web project in java
There is a large web project developed in java using spring and spring mvc. The project is assembled using maven, the project is made as a single maven module.
There was a need to cut it into parts (modules in maven terminology) so that you can make several assemblies, with a different set of modules, for different project installations (web functionality will also be cut into modules).
At the moment, there are two options for how to do this:
1) switch to servlet api 3.0 and build modules in the form of a jar with web-fragment.xml, packing jsp files and other resources there.
2) generate its own war file in each module, and then using the maven-assembly-plugin, assemble a large war file from several small ones.
Say "for" and "against" each option. Are there any better alternatives?
Answer the question
In order to leave comments, you need to log in
If we are talking about modularization in Java, then it is appropriate to recall OSGi supported by Spring.
This is where web application support is described. OSGi allows you to collect resources (classes, JSP, tld) from different modules or fragments. The description, however, looks somewhat complicated. In reality, everything is somehow simpler.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question