NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ
for more details.
I've been porting an older ADF 11g application to ADF 12c and used JDeveloper to do the migration for me, after a bit of code tweaking I tried to deploy the app only to find that it was failing with the java.lang.ClassNotFoundException: org.apache.myfaces.trinidad.webapp.TrinidadConverterELTag error. It took some time to find the culprit, so I've decided to share the fix.
The error looks like this:
The obvious issues to check here are:
- ADF installed in the WebLogic server
- ADF libraries correctly targeted for the server instance being deployed to
- weblogic-application.xml has a reference to the oracle.adf.domain shared library
In my case, all of the above were OK, so the issue was somewhere else.
I tracked it down to the deployment profile in JDeveloper. In my case, the EAR profile had these settings:
Some of the ADF and the Trinidad libraries were selected as Contributors, however the main ADF library was not, so some jar files were not being packaged. The solution was not to add extra libraries as contributors, but to deselect the ADF and Trinidad
libraries from being packaged into the EAR file.
If these are not packaged, the web-app will use libraries that are on the server via the oracle.adf.domain
shared library import. This fixed the issue with the deployment in my case.
Hope you found this post useful...
...so please read on! I love writing articles that provide beneficial information,
tips and examples to my readers. All information on my blog is provided free of
charge and I encourage you to share it as you wish. There is a small favour I ask in return however -
engage in comments below, provide feedback, and if you see mistakes let me know.
If you want to show additional support and help me pay for web hosting and
domain name registration,
donations, no matter how small, are always welcome!
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...