4 Replies Latest reply on Jul 31, 2007 5:40 PM by Anders Andersen

    HUSTON WE GOT A PROBLEM. JSF, portal, jboss-container. Sun R

    Anders Andersen Newbie

      I upgraded my portal from 2.6-CR1 to 2.6.1.GA

      Then the portal told me that MyFacesGenericPortlet did'nt exist any longer.

      1) Okay I could accept to add/change dependency lists when I upgrade.
      2) Okay I could accept to add some factory thing to my application ....

      But then searched this forum for "JSF AND myfaces" --> I got 9 pages of various issues.

      The problem seems to be that the jboss-container has switched from myfaces to Sun RI.

      One solution is to backport this change... Nice wiki (http://wiki.jboss.org/wiki/Wiki.jsp?page=Running2.6WithJBossAS4.2.xAndMyFaces)
      But NO NO NO NO.. what if another of my portlet suppliers uses Sun RI
      I am i chock that the page can exist. But anybody can write in the WIKI.. This cannot be a suggestion from the portal team?

      I cannot accept that my portlet is not running on 2.6.1.GA when I get to know the reason.
      This is simply not good enough.

      9 pages of issues....
      This tells me that JSF and the Portal has a bad story !!!!!
      It also tells me that issues around this area are going to explode. (It actually also does at Bea, but that is not a explanation .. more a reason to worry to have equal problems to Bea)
      It tells me that the portal is heading the wrong way !!!!!

      What can I accept?


      I can accept to add/change dependencies of my war
      I can accept to add some configuration to my-own-war NOT the jboss-system!!!!

      I can accept that the portal has a default JSF and that it changes !!!

      My suggestion -- bridges


      I suggest that the portal-project ensures these bridges.
      I suggest that the portal provide these bridges before such a change like the one in 2.6.1.GA !!!

      Therefore
      "Huston we got a problem"

      /Anders



        • 1. Re: HUSTON WE GOT A PROBLEM. JSF, portal, jboss-container. S
          Thomas Heute Master

          Hudson ? Calmed down now ?

          Ok we can talk.

          Your portlets can use different version of JSF (Some mYFaces 1.1.1, other myFaces 1.1.5, other myFaces 1.2.0, other Sun RI JSF 1.2 ...) Just embed them if you don't want to rely on the default embedded version.

          The bridges exist for myFaces and Sun RI.

          Now that said, you are talking about the bundle version. you can always use JBoss Portal 2.6.1.GA with JBoss AS 4.0.5 if you want (see the doc).

          Before calling the firefighters, make sure there is a fire.


          • 2. Re: HUSTON WE GOT A PROBLEM. JSF, portal, jboss-container. S
            Chris Laprun Master

             

            "anders3" wrote:
            Then the portal told me that MyFacesGenericPortlet did'nt exist any longer.
            ...
            The problem seems to be that the jboss-container has switched from myfaces to Sun RI.


            Yes.

            "anders3" wrote:
            One solution is to backport this change... Nice wiki (http://wiki.jboss.org/wiki/Wiki.jsp?page=Running2.6WithJBossAS4.2.xAndMyFaces)
            But NO NO NO NO.. what if another of my portlet suppliers uses Sun RI
            I am i chock that the page can exist. But anybody can write in the WIKI.. This cannot be a suggestion from the portal team?


            We need to update the wiki. The instructions were needed for people who wanted to use MyFaces instead of JSF RI at the AS level and still make sure it worked with Portal. Prior to 2.6.1.GA there was an issue with our JSF "meta" bridge so that was required. As of 2.6.1.GA, there shouldn't be anymore issues with bundling a JSF implementation with your portlets (e.g. MyFaces if you wish to use it instead of the Sun RI).

            In essence, the wiki is confusing as of 2.6.1.GA. There shouldn't be an issue with JSF anymore but if you do find one, please let us know.

            • 3. Sounds good. I can still use myfaces 1.1.1
              Anders Andersen Newbie

              I changed the scope in the war file from provided to nothing (default) so the artifacts becomes members of my war WEB-INF/lib

               <dependency>
               <groupId>org.apache.myfaces</groupId>
               <artifactId>myfaces-api</artifactId>
               <version>1.1.1</version>
               </dependency>
               <dependency>
               <groupId>org.apache.myfaces</groupId>
               <artifactId>myfaces-impl</artifactId>
               <version>1.1.1</version>
               </dependency>
              


              Maybe I misunderstood Thomas in another Forum answer here he writes that we are not supposed to have faces artifacts in the war because jboss have them.

              By the way this works... Now I can lanuch the application
              I get a warning


              01:33:06,411 WARN [JBossJSFConfigureListener] MyFaces JSF implementation found! This version of JBoss AS ships with the java.net implementation of JSF. There are known issues when mixing JSF implementations. This warning does not apply to MyFaces component libraries such as Tomahawk. However, myfaces-impl.jar and myfaces-api.jar should not be used without disabling the built-in JSF implementation. See the JBoss wiki for more details.
              


              I hope it still works. I will have to test my application again..


              • 4. Re: HUSTON WE GOT A PROBLEM. JSF, portal, jboss-container. S
                Anders Andersen Newbie

                By adding the following to my wars WEB-INF/web.xml
                The warning disappered


                <context-param>
                <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
                <param-value>true</param-value>
                </context-param>