Carsten Ziegeler wrote:

Ralph Goers wrote:

Carsten Ziegeler wrote:


But the other valid point remains: the syntax. Now, what about: ${cocoon.session.attributes.user.id} ?

Carsten

That's OK, but does that seems somewhat problematic. Does that mean that the code will search for a getXXX method (in this case getAttributes - Oh but it is getAttribute, not getAttributes) and when it finds it takes an argument it just uses the next field? Or is it just hard-coded to know that "attributes" is special?

Don't know :) Whatever is easier to understand and implement - I guess hard-code is easier?

I guess that's where I'm having a problem. From your example I presume "user" is an object that contains a getId() method? If "user" is an object that contains a Map would that also be accessed by
${cocoon.session.attributes.user.attributes.id} ?


Or am I going further than what is supported?

Ralph





Reply via email to