Hi Thomas, this sometimes happens at container startup if the container code invokes some SessionScoped event. But the Session is only available in a request of course. this should be in the code already since a long time (1.1.2 or so)
LieGrue, strub >________________________________ > From: Thomas Andraschko <[email protected]> >To: [email protected] >Sent: Friday, April 12, 2013 4:40 PM >Subject: Could NOT lazily initialize session context because of null >RequestContext > > > >Hi, > >i have many times this warning during development: > > >WARNING: Could NOT lazily initialize session context because of null >RequestContext > > >Why does this occur and how can i avoid it? >I never mentioned this error in my old application which runned perfectly with >1.1.6 (or 1.1.5, cant remember) > >Regards, >Thomas > > >
