1 Reply Latest reply on Feb 15, 2013 2:39 AM by Erdem YILMAZ

    websphere 4.3.0.Final ElResolver problem

    Erdem YILMAZ Newbie

      Hi,

      We have tried to use 4.3.0.Final with Websphere 8.0.0.3 and 8.0.0.5 versions. We have problem with El Resolvers. By the way richfaces 4.2.3.Final works perfect. We also changed amm.filter.properties file that ignores scanning of or.richfaces packages.

      when we add custom el resolver in faces-config.xml, 4.3.0.Final works like a charm. But in 4.2.3.Final, two same el resolvers exists but still working.


      faces-config.xml

      <el-resolver>org.apache.webbeans.el.WebBeansELResolver</el-resolver>

       

       

      is there any part that richfaces changes ElResolvers from javax.faces.application.Application? because websphere adds its el resolvers, view handlers programaticly like:

       

          private void setMyFacesApplicationCallbacks()

          {

              try

              {

                  ApplicationFactory factory = (ApplicationFactory)FactoryFinder.getFactory("javax.faces.application.ApplicationFactory");

                  Application a = factory.getApplication();

                  if(a != null)

                  {

                      a.addELResolver(new WebBeansELResolver());

                      a.setViewHandler(new ConversationAwareViewHandler(a.getViewHandler()));

                      if(TraceComponent.isAnyTracingEnabled() && tc.isDebugEnabled())

                          Tr.debug(tc, "Created OWB JSF ELResolver, View Handler, and ELContextListener");

                  } else

                  if(TraceComponent.isAnyTracingEnabled() && tc.isDebugEnabled())

                      Tr.debug(tc, "Application=null");

              }

              catch(Throwable e)

              {

                  if(TraceComponent.isAnyTracingEnabled() && tc.isDebugEnabled())

                      Tr.debug(tc, (new StringBuilder()).append("problems setting elresolver/handler/elContextListener: ").append(e.getMessage()).toString());

                  Ffdc ffdc = Manager.Ffdc.getFfdc(e, this, (new StringBuilder()).append(getClass().getName()).append(".setMyFacesApplicationCallbacks()").toString(), "45");

                  if(ffdc.isLoggable())

                      ffdc.log(new Object[0]);

              }

          }

       

      and in 4.3.0.Final version, this El resolver is not in the ElResolver list. Someone is removing it from the list.

       

      kind regards,

      Erdem

        • 1. Re: websphere 4.3.0.Final ElResolver problem
          Erdem YILMAZ Newbie

          Hi,

          We found the main cause. We were using org.richfaces.resourceOptimization.enabled in web.xml as:

           

                 <context-param>

                       <param-name>org.richfaces.resourceOptimization.enabled</param-name>

                       <param-value>false</param-value>

                 </context-param>

           

          When we remove optimization parameter, it works. It is important for us  especially in production?

           

          How can the resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere?

           

          kind regards,

          Erdem