This content has been marked as final. Show 2 replies
I've seen this as well, I've worked around it by uses EJBs.
Hmmm... might give it a try. Thanks for the hint.
For the time being I moved the initialization to session start (checking whether app is already initialized or not) via WebListener.