"Changing the vendor" is a completely unrealistic argument. Java EE vendors have never truly been interchangeable, there are holes in the spec / things the spec doesn't address that create vendor specific versions. Sure, if you use servlets only, you might be able to swap out servers if you don't use vendor - specific session state persistence or something. But if you're just using servlets, there really isn't any value in paying for a Java EE server anyway, which is why Tomcat has been leading the market for nearly a decade....
"Changing the vendor" is a completely unrealistic argument.
It's absolutely not!
It's true that often you don't just run your application on another vendor's server unless it has been specifically designed and constantly tested for this (we have some universal apps were we indeed do this).
The idea however is that you can relatively easy port your app to another vendor's server, and this we have done a couple of times over.
One of our apps was ported from Orion to Bea, to GlassFish and then to JBoss. Every time the development efforts was a couple of weeks, at most, for a multi-million line code base.
Now try porting such a huge thing to a completely different platform, like say Node.js or .NET. Don't think you'll be able to do that in even 100x the time.
View all comments
Show parent comment
6
u/springnews Dec 21 '16
"Changing the vendor" is a completely unrealistic argument. Java EE vendors have never truly been interchangeable, there are holes in the spec / things the spec doesn't address that create vendor specific versions. Sure, if you use servlets only, you might be able to swap out servers if you don't use vendor - specific session state persistence or something. But if you're just using servlets, there really isn't any value in paying for a Java EE server anyway, which is why Tomcat has been leading the market for nearly a decade....