well... yes and no... The container page needs to be valid xhtml (valid xml for that matter). If you put this div in it's own namespace, it still is. Compare it to having richfaces tags in an xhtml source page. Most editors do not know how to render all these namespaced tags anyway, so... With jsf the components spit out xhtml, and this is done in Chiba with an xslt. I do not see the difference and it is an Would have been nice to create an jsf component set that did this. I think it would have been faster I think, but not sure. But now I re-read your post... It is indeed selection based on an attribute, but how could I in my xforms module override the processing of the generic div? That is a bigger problem I think (and I do not want that) Choosing a template based on an attribute is not that important. That can always be done in java anyway... so... Another milestone reached just now.... I can make inputs read-only, hidden, invalid etc... based on attributes... look and feel done with css... this is way cool... Now I just should not forget refactoring things, since a lot can be put in a generic BaseXFormsTemplate. So little code remains.. well little... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213201#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...