-
1. Re: Warnings + other question
baradon Dec 31, 2010 10:54 AM (in response to sile)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
nbelaevski Dec 31, 2010 1:31 PM (in response to baradon)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 May 9, 2013 4:54 AM (in response to sile)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.