Hey Jim,
I've been working on editText again, with the latest nightly build from
today, the 25th.
I finally got it working with an action listener attribute... in a table...
all the behavior I wanted so far. Now there's one interesting issue...
From what I can tell from what I know of composite attributes, this
shouldn't be working... I like it, please don't fix it if it's a bug, but I
thought you might be able to explain the feature.
<a:editText id="description"
value="#{task.description}" size="45"
valueChangeListener="#{homeTaskTableBean.changeDescription}">
</a:editText>
Notice the valueChangeListener attribute... note that I am using your
default implementation with some minor CSS/JS updates, and an inputTextarea
instead of an inputText component... nothing special.
I never specified where to assign the valueChangeListener in the editText
composite component!
This is excellent, I like it.
If you guys are trending toward less configuration for the default set of
attributes in ezComp, please don't stop. I think this is excellent and will
help JSF2's adoption (if it's documented of course.)
PS. Is sun planning on putting up any kind of community JSF documentation? I
think it's much needed and will help build a userbase/community to promote
the product.
Thanks,
Lincoln