Fix for issue #40, session not present for Security Context persistence

If an application did not use a session yet (i.e. none is created), the Security Context is not persisted causing issue with subsequent request authentication. This is sometimes hard to debug since some other components may create a session under the hood (e.g. flash scope). This patch causes response wrapper to create a new session if none exists and if compatibility with Spring Security is enabled (in fact, the filter checks for Spring Security listener presence and passed true/false flag down to the wrapper).