Re: [jsr-314-open] #{cc} semantics
+1.
Also...
1. The user must recognize that the component in question is a
composite
component and code the expression differently. While at the moment it is
fairly easy to determine whether a particular component is a composite or
not (by looking at the namespace declaration), I think that we should strive
to blur these lines rather than reinforce them.
Exactly. We don't want the page author to start discriminating between the
implementations of a component. That's dangerous.
Leaving aside questions of how we might implement my preferred behavior for
the moment... Does anyone have comments on which behavior makes
sense from
a spec/end user perspective?
The general goal should be to make composite components as indistinguishable
from formal Java-developed components as possible.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
Attachments:
- attachment.html (text/html — 1.6 KB)