• Post Reply Bookmark Topic Watch Topic
  • New Topic

j2ee era max size

 
gianluca gian
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hello everyone, can you please tell me if there is a max size for an j2ee ear? Do you think that a size of 80 MB could be too much? The most of the size is given by libraries (50 MB). The application uses spring framework, axis, commons utilities etc. Have a good day.
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35709
408
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
While that sounds very large, I don't know of any max size. 50 MB of libraries sounds like a lot too. Are you using all the jars you deploy?
 
gianluca gian
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hello, I'm almost sure the application needs all of the libraries within the lib directory, maybe I could get rid of 2 or three... because of old functionalities that are not used anymore... I'm asking that because the client complains about the size... but I think he should thing more about the quality of the application then the size
 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree with you - the client's priorities are skewed. There is no maximum size that I am aware of either, though there will be limits on resources. Perhaps you should ask the cleint why they believe it is a problem?
 
Christian Gossart
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I don't know of a maximum size either (and it seems the JEE spec does not address this).
If your Ear is the only application deployed in the target server, and if your libraries do not change much (a fixed version for each lib for example), you can propose to add them in the server classpath.
That way, you only have to deploy the Ear with an empty lib directory, which will reduce its size.

 
Paul Sturrock
Bartender
Posts: 10336
Eclipse IDE Hibernate Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

If your Ear is the only application deployed in the target server, and if your libraries do not change much (a fixed version for each lib for example), you can propose to add them in the server classpath.

I would be cautious of that. You are kind of hardwiring your application and application server together.
 
Christian Gossart
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Paul you're right.

But I've seen clients deployment policies to be "one application per application server", and I also remember struggling with a Weblogic instance to have my specific version of a lib to be first in the classpath (that lib was used by WL too, and putting it in the EAR lib directory was clearly not enough).

Sure, if there are several application deployed in the same AS or domain, this solution can't work, as you'll probably mess with the other application lib dependencies, and if you change your dependencies versions at every build, it's not good either. But it's a proposition I'd consider while asking my client why 80 MB is too heavy



 
gianluca gian
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
sure, I think customer is looking for excuses because he does have money to pay my work! ....
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!