Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 396 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
MDS exception when deploying in Jdev 12.2.1
Hi experts,
I've installed Jdev 12.2.1 and I'm deploying my 12.1.3 ADF application into the new version of weblogic, and I'm getting this error related with MDS. MDS is currently configured and working fine.
<30-nov-2015 10H10' CET> <Error> <javax.enterprise.resource.webcontainer.jsf.application> <BEA-000000> <Error Loading Facelet cache: oracle.adfinternal.view.faces.facelets.rich.MDSFaceletCache
java.lang.InstantiationException: oracle.adfinternal.view.faces.facelets.rich.MDSFaceletCache
at java.lang.Class.newInstance(Class.java:427)
at com.sun.faces.application.ApplicationAssociate.createFaceletFactory(ApplicationAssociate.java:869)
at com.sun.faces.application.ApplicationAssociate.initializeFacelets(ApplicationAssociate.java:332)
at com.sun.faces.application.ApplicationAssociate.getCompiler(ApplicationAssociate.java:415)
at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:251)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NoSuchMethodException: oracle.adfinternal.view.faces.facelets.rich.MDSFaceletCache.<init>()
at java.lang.Class.getConstructor0(Class.java:3082)
at java.lang.Class.newInstance(Class.java:412)
at com.sun.faces.application.ApplicationAssociate.createFaceletFactory(ApplicationAssociate.java:869)
at com.sun.faces.application.ApplicationAssociate.initializeFacelets(ApplicationAssociate.java:332)
at com.sun.faces.application.ApplicationAssociate.getCompiler(ApplicationAssociate.java:415)
Truncated. see log file for complete stacktrace
>
Any idea if this is just a warning that can be ignored?
Thanks a lot in advance,
Jose.
Best Answer
-
It looks like this is caused by the following web.xml context parameter:
<context-param>
<param-name>com.sun.faces.faceletCache</param-name>
<param-value>oracle.adfinternal.view.faces.facelets.rich.MDSFaceletCache</param-value>
</context-param>
Try removing it, and the error will go away, it may be that the parameter is no longer valid... or something else is interfering.
Answers
-
If you can, purge the old MDS data as described at MDS Customization for JSF pages or https://docs.oracle.com/middleware/1213/core/ASADM/repos.htm#ASADM11531
You could also further analyse what's happening in MDS - see Troubleshooting Oracle Metadata Repository - 11g Release 8 Refresh 6 (11.1.8)
-
Hi Jose,
I am getting the same error. Were you able to find the cause ? Did you try Jiri's suggestion about purging the old MDS data.
Thanks,
Praveen
-
It looks like this is caused by the following web.xml context parameter:
<context-param>
<param-name>com.sun.faces.faceletCache</param-name>
<param-value>oracle.adfinternal.view.faces.facelets.rich.MDSFaceletCache</param-value>
</context-param>
Try removing it, and the error will go away, it may be that the parameter is no longer valid... or something else is interfering.