On 11/28/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > On 11/24/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > > > Another solution would be to add the getter/setters for these > > attributes to the component. I'm guessing that tree2 doesn't do this > > because you wanted to keep the html render-specific attributes out of > > the component and only access them in the renderer, and I can see the > > logic of doing so. > > You are correct about the reasoning. I think we should leave this part alone.
The standard JSF solution is to have a UITree2 component without getters/setters for anything HTML-specific, and an HtmlTree2 component that adds those getters/setters (and nothing else) purely for convenience. If tree2 followed this pattern, and you pointed the facelets tag name at that subclass, you'd have all you need. Regards, Adam Winer
