<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
My 2 cents....<br>
<br>
I'd rather see us pick a *standard value* for "a" ("ezcomp",
"compositeComponent" too long??, etc.). This is less confusing. Less
to worry about in the ezcomp declaration. Page author won't have to
worry about the EZComp author masking their values. And if scoping is
done correctly, this value won't exist automatically outside the
component which consumes it... so there's no name-space collision issue
here.<br>
<br>
If a mapping *is* desired to make it shorter in later references, I'd
suggest solving it more generically. For example, in JSFTemplating an
event handler can set a request attribute:<br>
<br>
<tt><event type="beforeCreate"><br>
setAttribute(key="a" value="#{compositeComponent.attributes}");<br>
</event></tt><br>
<br>
The above is not a proposal. I am trying to point out that there are
more generic easy solutions for this. I don't like the complexity
involved in a dynamic variable name -- it'll just confuse people. Keep
it simple.<br>
<br>
Ken<br>
<br>
<br>
Martin Marinschek wrote:
<blockquote
cite="mid:5a99335f0904122200q353d37e5qabf3636e79a7b3b6@mail.gmail.com"
type="cite">
<pre wrap="">Hi,
</pre>
<blockquote type="cite">
<pre wrap="">As I've mentioned when this has come up in the
past, my preferred solution would be to give the composite component
author the ability to define their own name/alias for
"compositeComponent.attrs" object (similar to the h:dataTable "var"
attribute). So, something like:
<composite:implementation attributesVar="a">
<h:graphicImage style="border: none" value="#{a.image}"/>
</composite:implementation>
</pre>
</blockquote>
<pre wrap=""><!---->
I second Andy's suggestion. My +1 for this approach.
regards,
Martin
</pre>
</blockquote>
</body>
</html>