-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: liferay-faces-2.1.5-ga6, liferay-faces-2.2.5-ga6, liferay-faces-3.0.5-legacy-ga6, liferay-faces-3.0.5-ga6, liferay-faces-3.1.5-ga6, liferay-faces-3.2.5-ga6, liferay-faces-4.2.5-ga6
-
Labels:None
{markdown}
The Liferay Faces Jars ordering configuration needs to be refactored. The ideal order would be:
*Inside*
((JSF Impl))
(Util)
(Bridge/Reslib)
(Alloy)
(Portal)
(Others) (ICEfaces, PrimeFaces, RichFaces, etc.)
*Outside*
*Note:* The most important part of this is that Util comes before Bridge and both come before everything else. Also Portal must come after Alloy. Other than that, the order should not matter.
However, this may be problematic because [Mojarra's ordering code is buggy and brittle](https://java.net/jira/browse/JAVASERVERFACES-3757). Since this ordering can be specified in many different ways, we should attempt to find a permutation which causes this ordering and doesn't cause Mojarra to throw exceptions or order the jars incorrectly.{markdown}
The Liferay Faces Jars ordering configuration needs to be refactored. The ideal order would be:
*Inside*
((JSF Impl))
(Util)
(Bridge/Reslib)
(Alloy)
(Portal)
(Others) (ICEfaces, PrimeFaces, RichFaces, etc.)
*Outside*
*Note:* The most important part of this is that Util comes before Bridge and both come before everything else. Also Portal must come after Alloy. Other than that, the order should not matter.
However, this may be problematic because [Mojarra's ordering code is buggy and brittle](https://java.net/jira/browse/JAVASERVERFACES-3757). Since this ordering can be specified in many different ways, we should attempt to find a permutation which causes this ordering and doesn't cause Mojarra to throw exceptions or order the jars incorrectly.{markdown}