...and here it is: the solution with bringing in an own JSF implementation:
You need to configure the server.xml in the following way:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<server description="new server">
<!-- Enable features -->
<featureManager>
<!-- <feature>webProfile-8.0</feature> -->
<feature>servlet-4.0</feature>
<feature>jsp-2.3</feature>
<feature>el-3.0</feature>
<feature>websocket-1.1</feature>
</featureManager>
<!-- To access this server from a remote client add a host attribute to the following element, e.g. host="*" -->
<httpEndpoint id="defaultHttpEndpoint"
httpPort="9080"
httpsPort="9443" />
<!-- Automatically expand WAR files and EAR files -->
<applicationManager autoExpand="true"/>
<!-- Default SSL configuration enables trust for default certificates from the Java runtime -->
<ssl id="defaultSSLConfig" trustDefaultCerts="true" />
</server>
Instead of using the "webProfile-8.0" (which includes the MyFaces environment 2.3) only reference these features that you really require.
The complete list of features of "webProfile-8.0" is available here: https://openliberty.io/docs/20.0.0.7/reference/feature/webProfile-8.0.html
- that's the one, we picked the reduced feature list from.
Now you can deploy CaptainCasa .war files without having to remove jsf-*.jar-files before.
THIS IS THE RECOMMENDED WAY TO USE CAPTAINCASA IN OPEN LIBERTY.