Christophe,
Why EL interprets it as an Interger. why not an attribute stored in request scope like it does for others ?
Refer to p-367 and 368...
Assume musicMap is a map and Genre is an attribtue. Also 1 is an attribute
${musicMap[Genre]} ----- Evaluates To ---> ${musicMap["Ambient"]}
Then
${musicMap[1]} --> If i have set "1" as an attribtue. Why it doesn't gets evalutes to it's value ?
Do you mean it first check inside [] for an integer (or not) then for whether it is an attribute ?
Why it doesn't treat attributes evaluation Genre and 1 alike ?
I know setting 1 as attribute is not a good idea but the exam may
test us on this as it's logically correct....