Ken Tam wrote:
2. In the control tutorial there is just a bean which is
instantiated (ie the first line of the test). For classes
which contain "@Control"
definitions is the "XXXClientInitializer" pattern above the
best way to initialize them? Or is there some kind of
container which does this automatically?
Yes and yes. The runtimes for all Beehive artifacts (controls,
pageflows, web services) contain code that automatically calls the
ClientInitializer class when necessary (actually, pageflows may still be
using private code dating back to before the ClientInit code was written
-- I know a JIRA issue exists to track updating that). The sweet spot
for controls usage in v1 is in those artifacts. We need to provide more
documentation here; my sense is that the ClientInitialization docs
should be primarily a part of the "container integration" docs, and only
peripherally a part of the "application developer" docs.
Glad you're making progress wading in :)
The ClientInitialization stuff isn't that important once you're actually
writing and using controls in a container. Right now there are a lot of
docs on what controls are and the cool things they can do. I think I
would just wish for a "Beehive Magic" section which quickly explains
whats happening behind the scenes. That way developers aren't expecting
some voodoo, but can more intelligently use the controls. Something
like "for classes which use controls a ClientInit class is generated
which takes care of the @Control, @EventSet, etc magic". :-) I really
might be an unusual case though...
Thanks,
- Dan
--
Dan Diephouse
Envoi Solutions LLC
http://envoisolutions.com/people/dan
