Changed OJDBC file path, but property still not found

reuppi

I am using the 8.0.24 PortalTemplate version and receive the following error: org.apache.myfaces.view.facelets.el.ContextAwarePropertyNotFoundException: org.apache.myfaces.view.facelets.el.ContextAwarePropertyNotFoundException: javax.el.PropertyNotFoundException: Property [isShowGlobalSearch] not found on type [ch.ivy.addon.portal.generic.bean.UserMenuBean]

The file and the property do exist.

I'm guessing this is happening because some of the axon ivy dependencies are configured incorrectly. E.g the OJDBC file pointed to the wrong path, which I fixed (updating the .classpath file). Now I am still getting the error. Is there an overview of files axon ivy requires so I can check which references I need to update or files similar to the ojdbc that are managed in the editor?

Reguël Wermelinger

do you use the official Portal:8.0.24, or your own fork/copy of it?
this could be an older bug, which has been fixed a long time ago, the latest Portal for LTS 8 is 8.0.38 https://market.axonivy.com/portal/8.0.38#download

reuppi

Hi Wermelinger, thanks for the quick response.
I am using the PortalTemplate from this thread https://community.axonivy.com/d/614-failing-to-download-portaltemplate-8024-snapshot-via-mavenaxonivycom/3. We are still using the 8.0.24 version of axon ivy engine and cannot switch right now, which is why I got the same version for the PortalTemplate. The PortalTemplate is working locally, which is why I thought of this being a configuration error rather than a PortalTemplate error.

lttung04

Do you know how to reproduce the problem, when this error occurs? If you use templates like frame-8.xhtml, you could refer to some examples in
https://nexus.axonivy.com/repository/maven-releases/ch/ivyteam/ivy/project/portal/portalExamples/8.0.24/portalExamples-8.0.24.iar
If you know how to reproduce, a sample project to reproduce the problem would be great.

reuppi

Ok, I am really late. If you'd like me to close the thread I will, but I'm unsure if I have yet fixed my problem. I went through the different classpaths of the different environments (local/dev/prod) and noticed that the older versions have had classpaths with exported=true while the local did not. I added these, tested the app and it is still working on local and dev. However, I can't release on prod right now and also: I do not think this is the final fix. Dev and local were working fine without this config, only once I released the project to prod it failed. I am going to further check whats going on.