
|
If you were logged in you would be able to see more operations.
|
|
|
|
doubleSelect template uses the name as the part of a javascript variable name, so when you use an ognl-style variable reference, the Group and Temp variables fail to work
----------------
See (from 2.2.2)
simple/doubleselect.ftl +38:
var ${parameters.name}Group = new Array(${parameters.listSize} + ${startCount});
for (i = 0; i < (${parameters.listSize} + ${startCount}); i++)
${parameters.name}Group[i] = new Array();
.... +72
var ${parameters.name}Temp = document.${parameters.formName}.${parameters.doubleName};
<#assign itemCount = startCount/>
<#assign redirectTo = 0/>
so if in your jsp you use:
<ww:doubleselect
...
name="foo.bar.id"
.../>
the generated javascript looks like
var foo.bar.idGroup = new Array(etc.)
....
var foo.bar.idTemp = document.myForm.doubleName
------------------------
${parameters.name} should probably be ${parameters.id}
|
|
Description
|
doubleSelect template uses the name as the part of a javascript variable name, so when you use an ognl-style variable reference, the Group and Temp variables fail to work
----------------
See (from 2.2.2)
simple/doubleselect.ftl +38:
var ${parameters.name}Group = new Array(${parameters.listSize} + ${startCount});
for (i = 0; i < (${parameters.listSize} + ${startCount}); i++)
${parameters.name}Group[i] = new Array();
.... +72
var ${parameters.name}Temp = document.${parameters.formName}.${parameters.doubleName};
<#assign itemCount = startCount/>
<#assign redirectTo = 0/>
so if in your jsp you use:
<ww:doubleselect
...
name="foo.bar.id"
.../>
the generated javascript looks like
var foo.bar.idGroup = new Array(etc.)
....
var foo.bar.idTemp = document.myForm.doubleName
------------------------
${parameters.name} should probably be ${parameters.id} |
Show » |
|
s/ ${parameters.name}Group/ ${parameters.id}Group/g
s/ ${parameters.name}Temp/ ${parameters.id}Temp/g
also
s/ ${parameters.name}Redirect/ ${parameters.id}Redirect/