Affects Version/s: 3.3.3
Fix Version/s: None
Component/s: Jawr Core
ServletContainer: Tomcat 6.0;
OS: Windows 7
When using JAWR.loader instead of the taglib, a new http session is opened as soon as the /jawr_loader.js script is loaded from the HTML page.
This also happens when the HTML page is explicitly set to not open a http session (e.g.: with <%@ page session="false" %>).
The question i am asking (despite of the technical facts i mentioned above) is:
Why is a http session needed when using jawr_loader? When using the taglib no session is opened and everything works as expected.