I would not remove the drop-in-war feature. Most of the times people first
adopt Tomcat and then look for enterprise level features. Drop-in-war
allows them to not rip and replace but simply adopt TomEE on their
existing Tomcat farm.
On Tue, May 19, 2015 at 4:47 PM, John D. Ament
David,
On Tue, May 19, 2015 at 6:29 PM David Blevins david.blev...@gmail.com
wrote:
What do people think about dropping the drop-in-war feature in .next?
It has had two use cases:
- allow users to use their own tomcat version and just add TomEE
- allow users to use TomEE in situations
+1 on the absolute but in practise it doesnt mean removing much code, maybe
OpenEJBListener and the listener facade but not much more isnt it?
2015-05-20 0:29 GMT+02:00 David Blevins david.blev...@gmail.com:
What do people think about dropping the drop-in-war feature in .next?
It has had two
I'm in favour of dropping it - its been many years since I last used it,
and I'm not aware of it being widely used (except the beanstalk question on
the mailing list earlier, but Docker with an unzipped TomEE bundle might be
a better solution anyway).
Jon
On Tue, May 19, 2015 at 11:29 PM, David
What do people think about dropping the drop-in-war feature in .next?
It has had two use cases:
- allow users to use their own tomcat version and just add TomEE
- allow users to use TomEE in situations where they don't have access to
modify the server (cloud)
It seems we can do the first
