About the log: originally it was not there and it is a nightmare to understand OWB is not well setup in your container. The log shouldn't happear - as much as you shouldn't even try to use session scope in a thread where it is not available theorically. A consensus can be to log it once but in "big" (like taking 20 lines of logs just to say something is not correct). A step further can be to return a fake context never active in such cases.
Wydt? Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2016-03-02 13:56 GMT+01:00 Thomas Andraschko <[email protected]>: > The method in deltaspike is ok, it just checks if the context is active in > the current thread. > > +1 for jira and a patch. > > 2016-03-02 13:47 GMT+01:00 Karl Kildén <[email protected]>: > >> Right, Deltaspike hides the ugly that you call a boolean method but >> instead of false you get ContextNotActiveException. One of the more >> mystical parts of the specification if you ask me. Maybe you are refereeing >> to how the BeanManager should behave if the thread is not managed? >> >> It is simply a little bit over my head but at least nothing in the >> javadoc for ContextUtils in deltaspike forbids usage from unmanaged threads >> and frankly if that was a requirement it seems like a poor idea to offer >> such static methods in the first place since managed threads have >> injectionpoints. >> >> Regarding a JIRA och a patch: I will take care of it. >> >> Thanks for helping me understanding this better >> >> cheers / Kalle >> > >
