On 25/06/2010 11:00 AM, Shan Syed wrote:
I don't know what your webapp does, so it's hard for me to describe how it
could be broken up; but personally, if I had a webapp that relied on 50
dependencies (and as a result, 50+ jars), I would try to identify how I
could modularize it and move the service layer to actual independent web
services or something, that are called/invoked by the actual front-end
Exactly!
50 dependencies is not hard to get to if you like Apache stuff and don't
like writing stuff that already exists.
Spring, Hibernate, Mysql, Tomcat
Commons-xxxx ---- easy to get 20+ of these just to support the above.
Add a few more in to support MS-Office docs, file uploads, etc.
Jasper
JSF
CXF
Jetspeed in our case since we are building portals.
Ron
On Fri, Jun 25, 2010 at 10:36 AM, Rajasekar Karthik<karthik...@gmail.com>wrote:
Shared library is a good option - will give it a try!
Most of the back-end functionality are services!
Breaking the webapp into multiple webapps?
Do you mean by functionality?
If not, what did you mean?
My disk speed is around 7200 RPM (SATA).
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Package-Speed-tp511260p511357.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
