Craig McClanahan schrieb: > 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. > Yes I was talking exactly the same issue over with Mario, definitely an area which as to be explored for the next JSP version, but for now having artefact codegens, via apt (probably a viable choice since it will be in 1.6 officially anyway) or via xdoclet2 and or velocity would be a good idea. The main point is just to have something which cuts down on the number of manual maintain artefacts. If there are codegen artefacts does not really matter.
> 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. > Well there are lots of areas coverable by decent codegens, facelet definitions generation comes to my mind. Thomas had something in this area already running.
