behavior simplification

I (David Geary) would like to see a simplification along the lines of the
simplifications we made to component development for JSF 2.0 with composite
components.

Ideally, it would be great if we could just implement, for example, a JS file
(like we now just implement a view template for composite components), and have
that transform into a behavior, complete with tag, that page authors can attach
to components, again, similar to the way we transform view templates with
composite component implementations into component tags.

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 DOM events).
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[2.0]

Start by reviewing the JSF 2.0 composite component implementation model and the existing behavior boilerplate described in the issue. Define how a JavaScript file would become an attachable behavior and tag, including the simple case without DOM-event handling; the issue provides no specific files or tests to run.

Written by the indexing model from the issue text.