I agree with you 100%. I had the same "pain" in legacy Web
applications. We even had the (business) need for mixing the technology
stack (legacy).
I used the term "fancy" as Spring(Boot) is (over)hyped at the moment :)
A lot of people will find and use it. You can see the (bad) questions
on
We are using an Application Server for our application - >15'000 classes >2000
db tables, on-premised deployed - and not planed to be a cloud system (legal
constraints).
An application server is a better fit for this kind of application with a very
long history / inception 1998.
Today, this
Last conclusion was :
Stay or go to JEE if you have to refactor a monolythic app - or if you have to
deliver on-premise systems that can't be on the couloud;
If you create a new cloud-based system, you may go to Spring boot, but keep in
mind that you have to understand the underlying required
It should work - but may not.
The situation I encountered is a war with all stacks of any ages within, mixed
etc.
If you put such a war in TomEE, it won't work at all, because of the different
serviceLoaders will be confused for loading implementations (Soap, Rest, etc)
On my side, developers
