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 [mailto:[EMAIL PROTECTED] >Sent: Sunday, February 26, 2006 05:00 AM >To: [email protected] >Subject: ADF Renderer-Kit and Tomahawk incompatibility > >Hi, >I'm using the latest version of Tomahawk (nightly) and ADF (10.1.3.04). >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); > .... >scroller.getChildren().add(link); > >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: > ><default-render-kit-id>oracle.adf.core</default-render-kit-id> > >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? >
