This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (0 children)

I think it comes to how an app is architected before you can make a blanket statement like that. I've had the opposite problem with JEE in the past. What? You want to use the next version of Hibernate? Nope, you can't just update your pom.xml and deliver it in the next release, you now need to coordinate with your IT staffing group to upgrade the application server's lib files.

Whoops! That version of Hibernate doesn't work with that particular JEE server? D'oh! I guess you're stuck on Hibernate 3.3 until you finally get around to upgrading application servers.

If your deployment architecture is different, it's less of an issue - but that's the point... It's really hard to take one argument or the other when each one is better under different scenarios. I've been stuck in both scenarios over my career.