Adam,
thank you for your help. This is the JSP code:
<body>
<f:view>
<h:form>
<t:dataTable id="mytable" rows="1" preserveDataModel="false"
value="#{TestBean.persons}" var="item">
<t:column>
<h:outputText value="#{item.name}"></h:outputText>
</t:column>
<t:column>
<h:outputText value="#{item.surname}"></h:outputText>
</t:column>
</t:dataTable>
<t:dataScroller for="mytable">
<f:facet name="next">
<h:outputText value="Show Next Values"/>
</f:facet>
</t:dataScroller>
</h:form>
</f:view>
</body>
As you can see, the t:dataScroller is inside a h:form.
But when oracle.adf.core is configured as default renderer kit, the
HtmlCommandLink which should surround the content of the facet "next" is
not rendered.
Adam Winer ha scritto:
FWIW, the ADF code has no problems with adding components
during Render Response - some of our components do just
that. We *do* replace the renderer for HtmlCommandLink, partly
so that our client-side validation code fires with h:commandLink
or af:commandLink, but also from some other issues that have
skipped my memory at the moment.
The only thing I can imagine in this specific instance if absolutely
nothing is rendering for it is that our replaced commandLink renderer
will refuse to do anything if it isn't inside of a form. If memory serves,
it logs a warning in this case. Could you check that you're using
a form (either h:form or af:form, we don't care which)?
-- Adam
