Hi, I want it to work the same way as cdi events normally works. I think the behavior in owb is a warn log that it could not be called.
> 13 sep 2014 kl. 13:33 skrev "John D. Ament" <[email protected]>: > > Karl, > > It's unclear whether or not you're expecting this to work. If you want > your exception handler to work when it's session scoped, you need to start > a session scope w/ CDI Ctrl. > > On Sat, Sep 13, 2014 at 5:05 AM, Karl Kildén <[email protected]> wrote: > >> Hello, >> >> SessionScoped @ExceptionHandler is this supported / considered normal >> practice? The problem is when the exception is from a job with no active >> sessionscope I get ContextNotActiveException. >> >> I was excepting a log message warning me that it could not send it for >> obvious reasons... My SessionScoped exceptionhandler collects information >> per user basis and it works smoothly when the exception was caused by user >> action. >> >> cheers >>
