[jboss-user] [Installation, Configuration & DEPLOYMENT] - Re: jboss-4.2.1 - seam-2.0 - myfaces classpath

[stan.silvert@jboss.com]

That message comes from Tomahawk.  You should be OK, but note that the WAR_BUNDLES_JSF_IMPL flag has not been tested with MyFaces 1.2.

If you want to get rid of that message and make sure you are totally safe, you can remove jsf-impl.jar and jsf-api.jar from deploy/jboss-web.deployer/jsf-libs.

Then, comment out the following in deploy/jboss-web.deployer/conf/web.xml:

  <!-- JBossInjectionProvider provides resource injection for managed beans. -->
  |   <!-- See JSF 1.2 spec section 5.4 for details.                             -->
  |   <context-param>
  |     <param-name>com.sun.faces.injectionProvider</param-name>
  |     <param-value>org.jboss.web.jsf.integration.injection.JBossInjectionProvider</param-value>
  |   </context-param>
  | 
  |    <!-- Configures JSF for a web application if the javax.faces.webapp.FacesServlet is declared -->
  |    <!-- in web.xml.                                                                             -->
  |    <listener>
  |      <listener-class>org.jboss.web.jsf.integration.config.JBossJSFConfigureListener</listener-class>
  |    </listener>
  | 
  |    <!-- Listens to all web app lifecycle events so that @PreDestroy can be called on -->
  |    <!-- JSF managed beans that go out of scope.  You can comment this out if you     -->
  |    <!-- don't use JSF or you don't use annotations on your managed beans.            -->
  |    <listener>
  |      <listener-class>com.sun.faces.application.WebappLifecycleListener</listener-class>
  |    </listener>
  | 
  |    <init-param>
  |            <description>JSF standard tlds</description>
  |            <param-name>tagLibJar0</param-name>
  |            <param-value>jsf-libs/jsf-impl.jar</param-value>
  |    </init-param>

I would also point out that the RI is much older and more likely to be stable.  Plus, the annotation processor is integrated with JBoss so you can use things like @PreDestroy and @PostConstruct on your managed beans.  You can also use JBoss Serialization to potentially speed up your application.  So I encourage you to give the RI a try.

There is really no reason to change the JSF implementation.  Would you like to use a different JSP implementation with JBoss?  I can show you how to do that too.  But nobody would think of such a thing!  The same goes for JSF.  It's now part of the container.

Stan Silvert
http://jsf.jboss.org

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067446#4067446

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067446