It should be well supported on any servlet 3.0 compliant container as its part of the specification. I suppose it could be inconvenient for application servers that already have OWB integration, but in that case I wouldn't expect the user to be including OWB in their application at all.
As long as we document that including the openwebbeans-web module into your application will cause a ServletContainerInitializer to automatically be added, I don't see any harm in it. I guess the only loss is some amount of ordering control you might have had if you included it in the parent web.xml directly. On Sat, Apr 25, 2015 at 5:14 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Le 25 avr. 2015 21:58, "Mark Struberg" <strub...@yahoo.de> a écrit : > > > > Hi! > > > > Should we add the WebBeansConfigurationListener (or later the two split > ones, see OWB-1055) into a web-fragment.xml inside our openwebbeasns-web > module? > > > > Pro: no need to add any listener manually + we should be neatly able to > define the default priorities (outermost listener). > > Con: not sure yet, that’s what I’m curious about :) Any input? > > > > Break container usage, not always well supported? > > That said could be done in another module. Would split lib and app > artifacts which is good. > > Also the conversation filter needs to be handled prog so > ServletContextInitializer sounds better. > > > > > LieGrue, > > strub >
