java - Is it more affective to keep general jars in server lib, then have it as part of war distribution? -


i in project, has multiple wars, similar dependencies: spring, hibernate, guava, e t.c. thinking of moving dependencies server lib folder optimization:

obvious downside of such approach

  1. this increase complexity of environment
  2. this increase complexity of dependencies management project.

there fore questions:

  1. is worth doing? (meaning there benefits,from performance , memory, point of view? (or it's headache))
  2. are there tools make such transition smoother?

i've seen go both ways. personally, prefer when dependencies packaged inside deliverable -- war/ear has spring, hibernate etc jars within itself. otherwise, need whole different release strategy manage dependencies deployed server, , may universe pity if ever need deploy incompatible versions of dependencies same service.

on downside, potentially increases duplication, these resources might exist in multiple webapps ... really, volume deploy application constrained?


Comments

Popular posts from this blog

basic authentication with http post params android -

vb.net - Virtual Keyboard commands -

css - Firefox for ubuntu renders wrong colors -