Or better compositeComponent.ez:nav.attrs of course we should have a way to distinguish between composite component attributes and all the other things in context.
Anyway, it looks like a kind of ancestor-or-self::name expression would solve the problem.
I wonder if EL wouldn't chalk at ':' in ".ez:nav."?.. Of course one can always use ['ez:nav'].
Probably, it could be made non-namespace aware if "ez:" is not specified, this would work in 99% of cases and be almost intuitive.. (#{compositeComponent.nav.attrs.label})
Other solution is to rewrite compositeComponent expressions on the parsing phase:
#{compositeComponent.attrs.label} to #{compositeComponent.ancestorOrSelf.nav.attrs.label})
[Message sent by forum member 'nzinoviev' (nzinoviev)]
http://forums.java.net/jive/thread.jspa?messageID=336984