> Thanks for reporting this. This is a new issue. The workaround is to > disable foreign key navigation methods using the following flag: > <navigationMethods>true</navigationMethods>
Of course, I meant disabling the flag: <navigationMethods>false</navigationMethods>
