Just an update for the curious on where things stand on the Facelets
support.
Ken and I have gotten support for <ui:composition>, <ui:insert> and
<ui:define> working, with much help and insight from Dr. qoob. The
remaining tags are
ui:component (creates a new UIComponent. trims)
ui:debug (do want to do this? I've never used and really have no
idea how it works :P)
ui:decorate (non-trimming ui:composition)
ui:fragment (non-trimming ui:component)
ui:include (think #include)
ui:param
ui:repeat
Those familiar with Facelets should know what trimming and non-trimming
mean. :) I think the remaining components should be pretty easy to
implement, given the groundwork laid with LayoutComposition.
I also added the Facelets DTD to the source tree and added an entity
resolver to the DocumentBuilder so the network is no longer hit when
loading the template or template client files.
Work is under way to change the component factories are managed to add
namespace support. This is pretty critical to completing the Facelets
support, as Facelets allows the user to specify the namespace in which a
certain set of components is exposed. Parsing of Facelets taglib.xml
files for components is, to the best of my knowledge, complete and
supports this change. I still need to test it to make sure the
components are successfully registered and are usable, though.
I think that's about it. Ken, qoob, please feel free to correct any
errors or misperceptions, and fill in any blanks I've missed.
-----
Jason Lee, SCJP
Senior Software Engineer
http://www.iec-okc.com <
http://www.iec-okc.com/>