JSF 2.2.x | useBundeledJsf | Payara 5 | dosent work / FISH-6519

[StevenHachel]

Hello,

I have already started a discussion about this in the payara forum. It is currently not possible to boot Payara 5.2022.2/3 with a Mojarra JSF 2.2.x. We are currently working with Primefaces and there are problems that occur when using Mojarra 2.3.x.

An excerpt from the thread... But now I’m trying to deploy Primefaces in this JSF 2.2 context, which fails. Do I have to configure something else in the web.xml so that Primefaces recognizes that the JSF 2.2 context is active here? Primefaces always searches internally for the JSF2.3 context.

Exception when deploying:

Exception while loading the app : java.lang.IllegalStateException: 
ContainerBase.addChild: start: org.apache.catalina.LifecycleException: 
java.lang.RuntimeException: java.lang.LinkageError: loader constraint violation: 
when resolving overridden method "org.primefaces.expression.impl.Jsf23WidgetVarSearchKeywordResolver.resolve(Ljavax/faces/component/search/SearchKeywordContext;Ljavax/faces/component/UIComponent;Ljava/lang/String;)V" the class loader (instance of org/glassfish/web/loader/WebappClassLoader) of the current class, org/primefaces/expression/impl/Jsf23WidgetVarSearchKeywordResolver, and its superclass loader (instance of org/apache/felix/framework/BundleWiringImpl$BundleClassLoader), have different Class objects for the type javax/faces/component/UIComponent used in the signature]]

Example: Primefaces JSF22](https://github.com/StevenHachel/glassfish-test-jsf22)

Steven

Payara 5.2022.2/3 Java SDK 8.332 Windows 10 / Debian 10/11

[JamesHillyard]

This is raised as a result of the feedback from https://github.com/primefaces/primefaces/issues/9080

[JamesHillyard]

Hi @StevenHachel,

I have raised this issue with the internal ID FISH-6519. We always encourage you to contribute, so if you feel confident to do so, then please raise a PR and a member of our development team will gladly review. Otherwise this issue will be picked up in the future.

Thanks, James

[StevenHachel]

Small information: Unfortunately, it still does not work in Payara 5.2022.4. :-(

Steven

[zubairAbubakar]

Hi @JamesHillyard, @StevenHachel

Apologies for crashing the party, but I have a similar "older situation". Basically, I have a legacy project that runs on GlassFish3 with JSF2.0 and I'm currently trying to move the project to Payara4. However, I'm also having trouble deploying as it seems Payara4 requires JSF2.2.

I've also tried useBundeledJsf but that doesn't seem to work, or is this feature only for Payara5?

At this point, any ideas or suggestions that you have would be greatly appreciated.

Thanks

[StevenHachel]

Small information: Unfortunately, it still does not work in Payara 5.2022.5. :-(

Steven

[100rabh]

@StevenHachel We are not facing this issue after upgrading to Payara Enterprise 5.57 (Tested and verified). I also think that it has been fixed for community version 6.2023.10 (check release-notes)

[StevenHachel]

Thank you for this information. :-)

[JamesHillyard]

Hi @StevenHachel,

As @100rabh rightly said, this issue has been fixed in Payara Community 6.2023.10 and Payara Enterprise 6.70 and 5.56.0. Thanks again for your patience while we resolved this issue