h:link, h:button is not working in richfaces 3.3.3 & JSF 2.0

[jithendrababu]

Hi,

I am using JSF2.0+Richfaces 3.3.3 in my project. I am getting run time issues while using the following tags.

• h:button
• h:link
• f:metadata
• f:viewParam

It just fails during runtime saying it can't find X component.

I do have jsf-api-2.0.2, jsf-impl-2.0.2, richfaces-api-3.3.3.final, richfaces-impl-jsf2-3.3.3.final, richfaces-ui-3.3.3.final, jsf-facelets-1.1.15, jstl-1.0 and obviously "xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" in every .xhtml file, am I missing something?

This is the exact error I'm getting:

<h:button> Tag Library supports namespace: http://java.sun.com/jsf/html, but no tag was defined for name: button

I have done the facelets configuration in web.xml as below.

<context-param>

        <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>

        <param-value>com.sun.facelets.FaceletViewHandler</param-value>

    </context-param>

    <context-param>

        <param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name>

        <param-value>true</param-value>

    </context-param>

There is no reference to JSF 1.2 anywhere in the project.

Can someone let me know the issue ? Is it the problem with Richfaces 3.3.3 or is there any context param to be set in the web.xml to make this work?

I have to do the bookmarking functionality in my project. Please help with your valuable suggestions.

[ilya_shaikovsky]

JSF 2 support in RF 3.3 is very limited. You may run your JSF 1.2 app just upgrading libs to JSF 2 but many new JSF 2 features will not be available because them depends on new VDL.

from http://community.jboss.org/wiki/RichFaces333AndJSF20 :

RichFaces 3.3.3 does not support JSF 2 built-in facelets (VDL)

Facelets 1.1.15 should still be used because of dependencies in RichFaces from the Tag Handlers classes.

JSF 2 native ajax problems

f:ajax

As RichFaces 3.3.3 does not supports VDL - it does not support any new tags like f:ajax, h:outputScript and so on.  You should continue to use the RichFaces equivalent tags where appropriate.