This content has been marked as final. Show 3 replies
1. Hmm, might be a JDev bug. If you remove jhsModel, and manually import it, do you then still have the same error. If so, it looks like a JDev bug.
2. Yes, I have noticed this as well. Typically, the sdolution is to open the AM and rebuild the model project. We will investigate whether there is way to always load the model objects prior to generation.
3. The authentication filter should only be added when you use custom security. What are your security settings in the app def?
Regarding 2: It seems that if I get this error and then regenerate with Jheadstart, it also messes up my AM by setting the superclass to JHSApplicationModuleImpl (instead of my custom superclass that extends JHSApplicationModuleImpl) and adding all the JhsAM functions to the AMClient (creating duplicates even!). I have even unchecked the 'Set AM superclass to JHSApplicationModuleImpl' setting so it should never happen anyway. It's a bit hard to reproduce so can't tell for sure, but this behavior is odd anyway since I am doing nothing out of the ordinary. Good thing we have Subversion revert for this though ;-)
Regarding 3: I use custom security for authorisation and authentication, so that was not the problem.
The "secure all pages" setting is only used in combination with ADF/JAAS security.
With custom security, the authentication filter by default always secures all pages.