Removing jsf prefix-mapping

modules/client/portal-client-tracing/src/main/java/de/cuioss/portal/tracing/PortalLogSpanHandler.java

@@ -78,7 +78,7 @@ public boolean doLogHandled(MutableSpan span) {
 
             @Override
             public boolean doLogHandled(MutableSpan span) {
-                if (requestPathContains(span, "/faces/")) {
+                if (requestPathContains(span, "/")) {
                     // report each page request
                     log.debug(span.toString());
                     return true;

modules/configuration/portal-configuration-api/src/main/java/de/cuioss/portal/configuration/CuiConstants.java

@@ -26,11 +26,6 @@
 @UtilityClass
 public class CuiConstants {
 
-    /**
-     * The currently active prefix for mapping jsf-views to the servlet: "/faces/"
-     */
-    public static final String FACES_VIEW_PREFIX = "/faces/";
-
     /**
      * The currently active prefix for mapping jsf-resources to the servlet:
      * "/javax.faces.resource/"

modules/configuration/portal-configuration-api/src/main/java/de/cuioss/portal/configuration/PortalConfigurationKeys.java

@@ -382,7 +382,7 @@ public class PortalConfigurationKeys implements Serializable {
      * views / partial trees that do not need any authentication in order to be
      * displayed, as comma separated list. Caution: The views are relative to the
      * root, usually starting with /faces. The distinct values are to be checked
-     * using String#startsWith(). The default for the portal is '/faces/guest/'. In
+     * using String#startsWith(). The default for the portal is '/guest/'. In
      * order to match all views you can use '/'.
      * </p>
      */
@@ -398,7 +398,7 @@ public class PortalConfigurationKeys implements Serializable {
      * templates that can be overridden by our template mechanisms. But what about
      * overriding pages that are delivered from the portal, e.g.
      * faces/guest/login.jsf? If a concrete application has its own pages like in
-     * pep using /faces/pep-ui/guest/login.jsf for login. Due to the deployment
+     * pep using /pep-ui/guest/login.jsf for login. Due to the deployment
      * mechanics of the portal faces/guest/login.jsf will still be accessible. In
      * order to deal with this issue the portal view suppression mechanics may be
      * used. Caution: The views are relative to the root, usually starting with
@@ -422,16 +422,16 @@ public class PortalConfigurationKeys implements Serializable {
     /**
      * Prefix for identifying context-parameter defining the restrictions for
      * certain roles: "portal.view.restrict.role.". The portal defines a view-level
-     * access rights-managements. All Views can be found under '/faces/'. The
+     * access rights-managements. All Views can be found under '/'. The
      * matching of certain views is checked using String#startsWith(). Therefore you
      * can omit any suffixes and define partial trees quite easily. The individual
      * views and/or subtrees can be separated by colons. If subtree is defined it
      * always has to finished by '/', in case of single page without '/'. A concrete
      * view restriction is always prepended by the string
      * 'portal.view.restrict.role.' Sample:
-     * portal.view.restrict.role.admin=/faces/admin/,/faces/content/verify will
-     * result in all views under '/faces/admin/' and the single view
-     * '/faces/content/verify.jsf' be only accessible if the user has the role
+     * portal.view.restrict.role.admin=/admin/,/content/verify will
+     * result in all views under '/admin/' and the single view
+     * '/content/verify.jsf' be only accessible if the user has the role
      * 'admin'
      */
     public static final String VIEW_ROLE_RESTRICTION_PREFIX = VIEW_BASE + "restrict.role.";
@@ -443,7 +443,7 @@ public class PortalConfigurationKeys implements Serializable {
      * Defines the view that are transient, therefore not part of the state saving.
      * Caution: The views are relative to the root, usually starting with /faces.
      * The distinct values are to be checked using String#startsWith(). The default
-     * for the portal is '/faces/guest/'. In order to match all views you can use
+     * for the portal is '/guest/'. In order to match all views you can use
      * '/'.
      * </p>
      */
@@ -467,7 +467,7 @@ public class PortalConfigurationKeys implements Serializable {
      * <p>
      * Defines the views that are to be excluded from the server-side history, as
      * comma separated list. The distinct values are to be checked using
-     * String#startsWith(). The default for the portal is '/faces/guest/'. In order
+     * String#startsWith(). The default for the portal is '/guest/'. In order
      * to match all views you can use '/'.
      * </p>
      */