3 Replies Latest reply on May 9, 2013 4:54 AM by Paolo Compieta

    Warnings + other question

    sile ! Newbie

      Hi,

       

      I'm using Richfaces 4, JSF 2 and Glassfish 3.

      I got two questions

       

      Question 1

       

      I got the following warnings in my project:

       

      Type 1:

       

      WARNING: JSF1074: Managed bean named 'a4j' has already been registered.  Replacing existing managed bean class type org.richfaces.VersionBean with org.richfaces.VersionBean.
      WARNING: JSF1074: Managed bean named 'a4jSkin' has already been registered.  Replacing existing managed bean class type org.richfaces.skin.SkinBean with org.richfaces.skin.SkinBean.
      WARNING: JSF1074: Managed bean named 'richSkin' has already been registered.  Replacing existing managed bean class type org.richfaces.skin.SkinBean with org.richfaces.skin.SkinBean.
      WARNING: JSF1074: Managed bean named 'ajaxContext' has already been registered.  Replacing existing managed bean class type org.ajax4jsf.context.AjaxContextImpl with org.ajax4jsf.context.AjaxContextImpl.

       

      Type 2:

      WARNING: JSF1091: No mime type could be found for file skinning.ecss.  To resolve this, add a mime-type mapping to the applications web.xml.

       

      Is there a way to avoid them?

       

      Question 2

       

      I use netbeans 6.9.1 and i have an xhtml page with:

      <rich:DataGrid value="#{loungeBean.games}" var="games" columns="2" id="gamesGrid">

       

      But the editor says: value, var, columns is not defined in the component's interface.

      Any suggestions?

       

      Thanks a lot!! If you need more information, shoot!

        • 1. Re: Warnings + other question
          Heiner Lamprecht Newbie

          Hi,

           

          regarding the second type of warnings, just add:

          <mime-mapping>
             <extension>ecss</extension>
             <mime-type>text/css</mime-type>
          </mime-mapping>

          to your web.xml.

           

          And regarding NetBeans:  I think, we have to wait until NetBeans supports RF4.  The way components are created is different in JSF 2 and JSF 1.2.  In former JSF 1.2, there was a config-file, that contained all the allowed attributes.  Now, with JSF 2, the IDE would have to scann all the classes with reflexion.

           

          But you can simply ignore these IDE warnings.  It does not effect rendering of the page.

           

          BR,

           

          Heiner

          • 2. Re: Warnings + other question
            Nick Belaevski Master

            Hi,

            Baradon Terendil wrote:

             

            Hi,

             

            regarding the second type of warnings, just add:

            <mime-mapping>
               <extension>ecss</extension>
               <mime-type>text/css</mime-type>
            </mime-mapping>

            to your web.xml.

            Since M5 this is not necessary.

            • 3. Re: Warnings + other question
              Paolo Compieta Newbie

              Hi,

              WARNING: JSF1074: Managed bean named 'a4j' has already been registered.  Replacing existing managed bean class type org.richfaces.VersionBean with org.richfaces.VersionBean.
              WARNING: JSF1074: Managed bean named 'a4jSkin' has already been registered.  Replacing existing managed bean class type org.richfaces.skin.SkinBean with org.richfaces.skin.SkinBean.
              WARNING: JSF1074: Managed bean named 'richSkin' has already been registered.  Replacing existing managed bean class type org.richfaces.skin.SkinBean with org.richfaces.skin.SkinBean.
              WARNING: JSF1074: Managed bean named 'ajaxContext' has already been registered.  Replacing existing managed bean class type org.ajax4jsf.context.AjaxContextImpl with org.ajax4jsf.context.AjaxContextImpl.

               

              i had the very same JSF1074 warnings when deploying a JSF2-compatible version of RichFaces3.3.3.Final (following guide at RichFaces 3.3.3 and JSF 2.0) - that is, when having both richfaces-impl-3.3.3.Final.jar and richfaces-impl-jsf2-3.3.3.Final.jar within the same WAR/EAR. Please, check for multiple JSF implementations in your deployable.