myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Byrne" <>
Subject Re: ADF Renderer-Kit and Tomahawk incompatibility
Date Sun, 26 Feb 2006 17:37:46 GMT
Please put this in the tomahawk JIRA; at least then it is recorded.  We currently don't have
an ADF category.

@devs - what are our options for *not* losing info like this?

Dennis Byrne

>-----Original Message-----
>From: Claudio Tasso []
>Sent: Sunday, February 26, 2006 05:00 AM
>Subject: ADF Renderer-Kit and Tomahawk incompatibility
>I'm using the latest version of  Tomahawk (nightly) and ADF (
>ADF requires the installation of its custom RendererKit 
>(oracle.adf.core), but it does not work well with some Tomahawk components.
>For example, let's examine the HtmlDataScrollerRenderer, which creates a 
>HtmlCommandLink during the  encoding  of the HtmlDataScroller component.
>This is the code which creates the HtmlCommandLink:
> HtmlCommandLink link = (HtmlCommandLink) application
>                        .createComponent(HtmlCommandLink.COMPONENT_TYPE);
> ....
>It seems to be quite standard: the compoent is created and the it's 
>added to the HtmlDataScroller componet.
>This code works very well when the faces-config.xml DOES NOT contain the 
>following line:
>But when this line is inserted, the HtmlCommandLink does not appear in 
>the rendered page which is sent to the browser as HTML.
>I suppose that the Oracle Renderer does not like that  a new component 
>is added to the component tree during the Render Response phase.
>So, my question is the following: who is wrong?
>I'm not a great expert of the JSF specification, but I don't rember 
>anything which forbids the dinamically creation of components during the 
>render response phase.
>Is it an ADF bug or a Tomahawk bug?

View raw message