Re: Handling bootstrap for mixed SE/Servlet scenario

we do something equivalent in meecrowave since we start cdi before servlets to support listener injections so we extend the listener and impl contextInitialized as a noop think it is quite specific to vendors and if you think a bit more you just need a start/stop abstraction which is already the

Re: Handling bootstrap for mixed SE/Servlet scenario

Ok, so in the end I did have to sublcass WebBeansConfigurationListener. The issue I ran into was that in contextInitialized you're attempting to start the application. Since I do my servlet initialization in a @Observes @Initialized(ApplicationScoped.class) callback, OWB was firing the event that

Re: Handling bootstrap for mixed SE/Servlet scenario

Nevermind, I forgot about openwebbeans.properties. Mix and match for the win. John On Mon, Dec 26, 2016 at 11:55 PM John D. Ament wrote: > Hi, > > So let's say I'm using Tomcat embedded and OWB. I bootstrap OWB using its > normal function, and I have impl, web and

Handling bootstrap for mixed SE/Servlet scenario

Hi, So let's say I'm using Tomcat embedded and OWB. I bootstrap OWB using its normal function, and I have impl, web and resource on my classpath. When I ask for the ContainerLifecycle service, I get back a WebContainerLifecycle since I have web on the classpath. So I'm wondering, does it make