On Fri, Jun 15, 2012 at 4:50 PM, Marcus Bond <[email protected]> wrote: > I was following the example on the website in regard to subjects and in > particular creating a subject for use in executing a different thread using > “new Subject.Builder()..” and have been hitting the exception > > java.lang.IllegalArgumentException: SessionContext must be an HTTP > compatible implementation. > > Same thing applies when I use WebSubject.Builder(). In fact the code > definitely shouldn’t use WebSubject anyway since this is in a service layer > component that has no awareness that it is running in a web app. > > I thought about using a separate security manager for this but then read > that only one security manager per application is recommended… This kind of > thing must have been solved before, any ideas please?
Yep, see my post from yesterday ;-) http://shiro-user.582556.n2.nabble.com/Using-non-web-based-sessions-from-within-a-web-application-s-background-jobs-td7577505.html Regards, Thilo
