Mojarra Error Liferay 6.2.2GA3

[jose fernandez，修改在9 年前。]

when starting Liferay 6.2.2GA3 on Tomcat 7.0.42 on an almost OOTB bundle I can see the trace below. The bridge is a correct version but the error for the upgrade of the Mojarra version still on the logs. Is this a regression?

886 16:23:03,432 INFO [localhost-startStop-1][PortletHotDeployListener:344] Registering portlets for dailytips
887 16:23:03,465 INFO [BridgeImpl] Initializing Liferay Faces Bridge 3.2.4-ga5 (Ephesus / Feb 15, 2014 AD)
888 16:23:03,664 INFO [BridgeImpl] Initializing Liferay Faces Bridge 3.2.4-ga5 (Ephesus / Feb 15, 2014 AD)
889 16:23:03,665 INFO [BridgeImpl] Initializing Liferay Faces Bridge 3.2.4-ga5 (Ephesus / Feb 15, 2014 AD)
890 Loading file:/mnt/data/opt/node1/tomcat-7.0.42/temp/31-dailytips/WEB-INF/classes/portlet.properties
891 16:23:03,681 INFO [localhost-startStop-1][PortletHotDeployListener:497] 3 portlets for dailytips are available for use
892 SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
893 SLF4J: Defaulting to no-operation (NOP) logger implementation
894 SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
895 Mar 9, 2015 4:23:04 PM org.apache.coyote.AbstractProtocol start
896 INFO: Starting ProtocolHandler ["http-bio-8088"]
897 Mar 9, 2015 4:23:04 PM org.apache.coyote.AbstractProtocol start
898 INFO: Starting ProtocolHandler ["ajp-bio-8008"]
899 Mar 9, 2015 4:23:04 PM org.apache.catalina.startup.Catalina start
900 INFO: Server startup in 212067 ms
901 16:24:04,820 WARN [BridgeSessionListener:169] Unable to cleanup ViewScoped managed-beans upon session expiration. Please upgrade to Mojarra 2.1.18 or newer. For more info, see: http://issues.liferay.com/browse/FACES-1470
902 16:24:04,845 WARN [BridgeSessionListener:169] Unable to cleanup ViewScoped managed-beans upon session expiration. Please upgrade to Mojarra 2.1.18 or newer. For more info, see: http://issues.liferay.com/browse/FACES-1470

The portlet is a simple JSF with PrimeFaces.
The dependencies versions are:

<properties>
.....
<liferay.version>6.2.2</liferay.version>
<primefaces-version>4.0</primefaces-version>
<liferay-jsf-bridge>3.2.4-ga5</liferay-jsf-bridge>
<jsf-version>2.2.8</jsf-version>
</properties>

the jars on the lib folder are:

jsf-api-2.1.21.jar
jsf-api-2.1.jar
jsf-impl-2.1.3.jar
liferay-faces-bridge-api-3.2.4-ga5.jar
liferay-faces-bridge-impl-3.2.4-ga5.jar
liferay-faces-portal-3.2.4-ga5.jar
liferay-faces-util-3.2.4-ga5.jar
primefaces-4.0.jar

As confirmed in http://issues.liferay.com/browse/FACES-1470 the issue is solved, I'm looking all the aspects and I cannot see where is the issue.

Can anybody help with this?

José

[Juan Gonzalez，修改在9 年前。]

Hola Jose,

as stated in Liferay Faces version scheme Liferay Faces 3.2.x (your current version) should be used under JSF 2.1 + Liferay 6.2.

Seems in your pom.xml you want to use JSF 2.2, so first of all, which JSF version do you want to use?

Liferay Faces portlets requires some configuration to be applied. If you create your JSF portlet through Liferay IDE or Liferay Faces maven archetypes it should be ok, but as seen on your pom.xml JSF version, this isn't applied in your generated WAR. How did you create your portlet?

Do you have some duplicated jars in your lib folder (jsf-api) and doesn't fit with the jsf-impl version you have. I guess this is caused by not creating your portlet properly, waiting four your answer on previous point.

[jose fernandez，修改在9 年前。]

Gracias Juan,
.
The duplicated library is due to a version modification and not undeploying the portlet properly.

We want to use:
Liferay Faces Version JSF Version (Major1) Liferay Portal Version (Major2)
3.2.x 2.1 6.2

Corrected the pom to
<jsf-version>2.1</jsf-version>

Also the error on the pom is due to the stress trying to solve the issue.

We cannot deploy now on the server, if this doesn't help I'll comeback.

Cheers.
José

[Neil Griffin，修改在9 年前。]

Your deployment should only have the following jars related to Mojarra:

WEB-INF/lib/jsf-api-2.1.21.jar
WEB-INF/lib/jsf-impl-2.1.21.jar

		<dependency>
			<groupid>com.sun.faces</groupid>
			<artifactid>jsf-api</artifactid>
			<version>2.1.21</version>
		</dependency>
		<dependency>
			<groupid>com.sun.faces</groupid>
			<artifactid>jsf-impl</artifactid>
			<version>2.1.21</version>
		</dependency>

For more info, see the pom.xml descriptor from the Liferay Faces JSF Maven Archetype.

[jose fernandez，修改在9 年前。]

Hi,

To sort out all conflicts on versions we have use the Maven archetype that has set the correct version for all the components. The error is not anymore on the logs

Thanks for the help.
José

[Juan Gonzalez，修改在9 年前。]

Glad you have it working.

Creating the portlet through Liferay IDE or Liferay Faces Maven archetypes is always the best way for avoiding WAR packaging errors like these.

[Juan Gonzalez，修改在9 年前。]

Moved to Liferay Faces category