Jsf warn about nested tag

Question

hi I try to make a dynamic data table wtih jsf 1.2; When I run my pr�ject on the server I have gor this warn in my server log.�s there ther e somebody who know this problem.
My datatable code:
<h:column id="column11" >
<f:facet name="header" > </f:facet>
<h:commandButton action="#{RefKayit. detaysil} " rendered="#{ RefKayit. edit1}" image="img/x. gif" id="s"></h:commandB utton>
<h:commandButton action="#{RefKayit. detaysil1} " rendered="#{ RefKayit. edit}" image="img/x. gif" id="ss"></h: commandButton>
</h:column>
warn on the server log:
23519: 09:21:18,551 WARN [HtmlResponseWriter Impl] HTML nesting warning on closing td: element input rendered by component : {Component-Path : [Class: javax.faces. component. UIViewRoot, ViewId: /TestReferansTanim. jsp][Class: javax.faces. component. html.HtmlForm, Id: tref][Class: javax.faces. component. html.HtmlDataTab le,Id: update][Class: javax.faces. component. html.HtmlColumn, Id: column11][Class: javax.faces. component. html.HtmlCommand Button,Id: ss]} not explicitly closed
thanks
how can � solve this warn?

Answer 1

My guess is that you're not resetting state in the parent tag handlers (e.g., data set by the nested tag handlers) correctly for them to work with tag handler pooling. For some more info on this, see an article I wrote for ONJava.com a while back (the "Tag handler life cycle and instance reuse" section):
http://www.onjava.com/pub/a/onjava/2001/11/07/jsp12.html?page=2
or my JavaServer Pages book (O'Reilly), plug plug :-)
http://www.thejspbook.com/
Tomcat 4.1.x uses tag handler pooling by default, but LiteWebServer (which is my company's product, BTW) disables pooling by default. Not sure about Jetty, but it's likely that it also disables pooling. For Tomcat 4.x and LiteWebServer, you control pooling through an init parameter to the JSP servlet in the conf/web.xml file:
    <servlet>
        <servlet-name>jsp</servlet-name>
        <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
        <init-param>
            <param-name>enablePooling</param-name>
            <param-value>false</param-value>
        </init-param>
    </servlet>I suggest that you disable pooling in Tomcat first and see if that helps. If so, you know what the problem is and can use the hints in my article to fix it.
Hans Bergsten (JSP and JSF EG member)