Oops, sorry, my bad, I let that slip through the cracks. I'll be more diligent from here on out.
Thanks,
david
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=701
It only takes about 1 minute to create an issue, so I encourage members that are drafting an e-mail in defense of an idea to save 60 seconds to create the issue if it doesn't exist ;)
Be sure to set the milestone to 2.1. The default milestone is currently 1.2, which is obviously irrelevant.
-DanOn Tue, Dec 8, 2009 at 1:34 PM, Jim Driscoll <Jim.Driscoll@sun.com> wrote:
On 12/7/09 12:44 PM, Lincoln Baxter, III wrote:Yes, please file it.
+1, I think this should go right into the issue tracker
On Dec 7, 2009 3:06 PM, "David Geary" <clarity.training@gmail.com<mailto:clarity.training@gmail.com>> wrote:
There does seem to be a fair bit of boilerplate (20+ lines) that you have to add to every single component that you want to be behavior aware. It should be possible to capture that for the simple case, at least (i.e., the component is otherwise not operating on any DOM0 events).
Also, I noticed that Jim Driscoll's post about implementing custom
behaviors seems to have copied a good deal of code right out of the
RI. Could we make that code accessible to developers so they don't
have to reinvent?
Jim
--
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