Nope, we DO also handle contexts. Those are 2 different aspects. The first one is booting - this obviously only makes sense in SE. The other one is ContextControl - and this also should work in EE.
But please note that we only have a few backends yet: weld, owb and openejb. There is no wildfly nor glassfish backend YET. Means that the cdictrl-weld _might_ work in glassfish, jbossas or wildfly, but it is *not* guaranteed. It _would_ be easily possible to write backends for those containers. I'd be happy about some contributions ;) LieGrue, strub On Wednesday, 21 May 2014, 14:23, Matt Benson <[email protected]> wrote: > > >On rereading your original message, you should be able to manage custom >contexts using appropriate extensions regardless, but the cdictrl module, >AIUI, is concerned with bootstrapping. > >Matt > >On May 21, 2014 7:20 AM, "Matt Benson" <[email protected]> wrote: > >> In an EE container CDI should just "be"; you only have to bootstrap it >> outside an EE or EE web profile container. >> >> HTH, >> Matt >> On May 21, 2014 6:29 AM, "Gunzenreiner Simon" < >> [email protected]> wrote: >> >>> Hi >>> >>> Am I right in understanding that the Deltaspike context control API for >>> weld is only available for Weld SE? There seems to be no "binding" for Weld >>> in an EE context, specifically JBoss. >>> >>> It would be nice if the doc would make that more clear, maybe the weld >>> binding could even highlight this in the name (deltaspike-cdictrl-weld-se >>> instead of deltaspike-cdictrl-weld). >>> >>> Are there any plans to support the context control API also in the EE >>> context? My use case is the following: I have a "stateful" Object that >>> should survive multiple user interactions and is therefore >>> ConversationScoped. The same managed bean should also be usable in >>> situations where we have only an active request scope (EJB timer), and it's >>> life cycle should then be bound to the request scope. For this case, I >>> would like to activate the Converation scope when the timer method is >>> entered programmatically (or rather via an Interceptor). >>> >>> Regards >>> Simon >>> >> > > >
