Hi again,
I was thinking about this again a few minutes ago and thought maybe using
an object that implements Map is not the solution, maybe if I use a List
implementation, then OGNL will not interpret ".value" as get("value") since
you can't do that to a List.
Indeed getValue() was called using a
> Result is
>
> During get
>
> >> getIndex()
> >> getIndex()
> >> getFieldMap()
> my...@1.get(1)
> my...@2.get(1)
> my...@3.get(value)
> >> getIndex()
> >> getIndex()
>
> Ok, getValue() isn't called, I can work with this, I can make all my
keys
> numbers, if I detect a non-number I just route t
My case is logically like this
Imagine these data structure
gamer:
userId
gameConsole
type
game:
gameId
gameName
A game is associated to a gameConsole
There are 2 types of gamers,
for a type = CASUAL gamer, there are no games associated
for a type = AVERAGE gamer, you can have games asscociated
3 matches
Mail list logo
