one more.
In Tomahawk, we check against the component-type/family (which are String based)
-M
On 6/25/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
Trinidad's hierarchy is
javax.faces.component.UIComponent
UIXCOmponent
UIXComponentBase
...
Trinidad also uses the standard interfaces, like EditableValueHolder
or ValueHolder.
Unfortunately there is no Form interfaces, so that some JSF component
libs do a instanceof UIForm, which doesn't work with Trinidad.
But... h:form works fine with Trinidad as well.
-M
On 6/25/07, Renzo Tomaselli <[EMAIL PROTECTED]> wrote:
> Hi, I met some troubles while enclosing rich:dropDownMenu components
> inside a tr:form. The involved renderer complains about not being able
> to find an enclosing form.
> That component expects to be enclosed by a standard UIForm somewhere
> high in the component tree, while Trinidad tr:form places a UIXForm
> class there (actually a CoreForm class).
> Tr:form was mandatory while using Trinidad because of reasons I can't
> remember right now.
> Just trying to understand what is standard and what is not in this puzzle.
> Could anybody enlight this topic please ?
> Thanks -- Renzo
>
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
