Following is the issue I faced while developing application in latest ADF 12.2.1 release. This issue came after running an application with single blank page based on responsive page template.
com.sun.faces.context.FacesFileNotFoundException: /oracle/templates/responsiveTemplate.jspx Not Found in ExternalContext as a Resource
at com.sun.faces.facelets.impl.DefaultFaceletFactory.resolveURL(DefaultFaceletFactory.java:270)
at com.sun.faces.facelets.impl.DefaultFacelet.getRelativePath(DefaultFacelet.java:283)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:348)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)..........
This issue was faced when Maven was selected as deployment descriptor on the last step of creating ADF application. If we create the application with default deployment option then this issue will not be faced. As in second scenario JDeveloper automatically adds the required "Oracle Page Templates" library to the project properties. However, in case of application using Maven, the library dependency was not added automatically in pom.xml file. Bad news was, even after adding the "Oracle Page Templates" in pom.xml, the issue was not resolved.
So the only solution for this issue was to create the application with default deployment option.
com.sun.faces.context.FacesFileNotFoundException: /oracle/templates/responsiveTemplate.jspx Not Found in ExternalContext as a Resource
at com.sun.faces.facelets.impl.DefaultFaceletFactory.resolveURL(DefaultFaceletFactory.java:270)
at com.sun.faces.facelets.impl.DefaultFacelet.getRelativePath(DefaultFacelet.java:283)
at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:348)
at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)..........
This issue was faced when Maven was selected as deployment descriptor on the last step of creating ADF application. If we create the application with default deployment option then this issue will not be faced. As in second scenario JDeveloper automatically adds the required "Oracle Page Templates" library to the project properties. However, in case of application using Maven, the library dependency was not added automatically in pom.xml file. Bad news was, even after adding the "Oracle Page Templates" in pom.xml, the issue was not resolved.
So the only solution for this issue was to create the application with default deployment option.