Craig McClanahan wrote:
I was constrained in the stuff so far by what could be accomplished at
runtime -- and there's no way to define a tag library "on the fly" at
that point. But what you're describing could certainly be done by
processing annotations at compile time instead (using "apt" or
equivalent). That'd be an interesting area to explore, over and above
the runtime stuff.
I'm wondering if you couldn't provide a custom TagLibrary to Facelets
(implements TagLibrary) that will lazily look up UIComponents from some
other entity available on the ThreadLocal via the FacesContext to have
them compiled into the page on first request.
I'm game to work on that for Shale. There's a couple of other useful
things to do at compile time ... like a tool to audit the
configuration files that do exist to catch silly mistakes like wrong
class names for managed beans.
With a good use of annotations we could cut down from two xml
definitions and 3 classes, to two classes and 1-2 annotations in the
controller and view.
Which means a total cut down of the code of at least 30% average and a
total cutdown of artefacts from 5 to 2.
Craig
--
--------------------------
Sent from my FrankenBerry Wireless Handheld
