1 2 Previous Next 19 Replies Latest reply on Feb 5, 2014 6:50 PM by Farah Juma Go to original post
      • 15. Re: Internal Server Terror from multi-JSF attempt
        Stan Silvert Master

        Rob,

         

        Are you using ICEfaces?

         

        I don't know if Nicklas ever solved his ICEfaces problem, but as far as I know there are no issues with Multi-JSF on WildFly.  Everything should be working properly so you should be able to use MyFaces 2.1.3.

         

        See Design of WildFly Multi-JSF feature

         

        Stan

        • 16. Re: Internal Server Terror from multi-JSF attempt
          Rob Gosling Newbie

          Hi Stan,

           

          No, we are only using MyFaces at this time - we're minimizing the number of changes as much as possible.  I should have pointed out we are migrating from JBoss 4.0.5 to Jboss 7.2/EAP 6.1.Alpha.  I did work around the issue by your earlier note about the MyFaces impl jar did not have the jsf.js file.

           

          The MyFaces code is looking for jsf.js.  Interesting thing is that Mojarra stores this file in the impl jar while MyFaces puts it in the API jar.  There is one difference in the way the impl and api jars are added to the deployment by the JSF subsystem.

           

          I ended up adding it to the Impl jar and everything seems to be working so far.  I don't like adding it (as I don't like modifying third party jars) but didn't see a workaround other than that for the time being.  Does the latest Wildfly work around this issue?

           

          Thanks
          Rob

          • 17. Re: Internal Server Terror from multi-JSF attempt
            Tomas Remes Expert

            I am still facing this issue too and I can agree with Rob. I am using only MyFaces and I've tried out 2.1.14 and 2.2.0-beta versions  also in WildFly CR1 (e.g. defining "default-jsf-impl-slot="myfaces-2.2.0" in standalone config) . If I am not missing anything, there is no workaround at the moment.

            • 18. Re: Internal Server Terror from multi-JSF attempt
              Stan Silvert Master

              Tomas Remes wrote:

               

              I am still facing this issue too and I can agree with Rob. I am using only MyFaces and I've tried out 2.1.14 and 2.2.0-beta versions  also in WildFly CR1 (e.g. defining "default-jsf-impl-slot="myfaces-2.2.0" in standalone config) . If I am not missing anything, there is no workaround at the moment.

              I suspect that you are indeed missing something.  This should be all fixed in the latest WildFly.  See Design of WildFly Multi-JSF feature.

               

              Stan

              • 19. Re: Re: Internal Server Terror from multi-JSF attempt
                Farah Juma Apprentice

                Adding the following <imports> section to the "javax.faces.api" dependency in <JBOSS_HOME>/modules/com/sun/jsf-impl/<MYFACES_SLOT>/module.xml should solve the problem:


                <module name="javax.faces.api" slot="${MYFACES_SLOT}">
                    <imports>
                        <include path="META-INF/**"/>
                    </imports>
                </module>
                


                This allows the MyFaces implementation module to access the jsf.js file from the MyFaces API module.

                1 2 Previous Next