WiqueryGeneratedJavaScriptResourceReference causes errors in tomcat (cookies set to false -> identification over jsessionid in url) cluster (startet at version 1.1.x)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. use generated WiqueryGeneratedJavaScript code (e.g. modal dialog) in a page
2. deploy the application in an tomcat cluster (including load balancer) where 
cookies set to false and the identification is handled by the urlrewriting of 
jsessionid in the url
3. inspect the source code of the resulting webpage

What is the expected output? What do you see instead?
something like this:
expected something like this:
<script type="text/javascript" 
src="resources/org.odlabs.wiquery.core.commons.WiqueryGeneratedJavaScriptResourc
eReference/1291276644108wiquery-gen.js;sessionid=14F5C1833D72D54E3EC8D6DCB094ABF
E"></script>
got:
<script type="text/javascript" 
src="resources/org.odlabs.wiquery.core.commons.WiqueryGeneratedJavaScriptResourc
eReference/1291276644108wiquery-gen.js"></script>

Our problem at this place is, that the load balancer do not know to which 
tomcat this javascript belongs and may balance the request to a tomcat where 
the generated js is not available.

What version of the product are you using? On what operating system?
1.1.x

Please provide any additional information below.

Original issue reported on code.google.com by unterst...@gmail.com on 2 Dec 2010 at 8:00

[GoogleCodeExporter]

I've got a similar problem with the new way of rendering the statements.
Since my company doesn't use sticky sessions, I can't use Wickets shared 
resources when they're created at run-time (not in the Application's init()).
I've added a settings option to enable the old behavior in my copy of WiQuery. 
Please find the patch attached. Maybe the WiQuery team can add this if there 
are no arguments against it.

Original comment by norc...@gmail.com on 6 Dec 2010 at 2:37

Attachments:

• wiquery-patch.txt

[GoogleCodeExporter]

Hi there. I had a similar problem and the patch just helped me out. Please 
integrate the fix! :)

Original comment by Steff.F...@googlemail.com on 7 Dec 2010 at 7:06

[GoogleCodeExporter]

Hi,

I will check the patch to see if your fix can be apply. Really thank you for 
your contribution.

Cheers

Julien Roche

Original comment by roche....@gmail.com on 7 Dec 2010 at 7:48

• Changed state: Accepted
• Added labels: Milestone-Release1.2

[GoogleCodeExporter]

Fix in commit r609

Original comment by roche....@gmail.com on 8 Dec 2010 at 9:37

• Changed state: Fixed

[GoogleCodeExporter]

Thanks a lot!

Just tested our application against the trunk and everything worked fine.

Cheers

Johannes

Original comment by unterst...@gmail.com on 9 Dec 2010 at 10:36