New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nullptr when using shared configuration #1180
Comments
@sjaakd with the correct line it makes much more sense :). Does this mean that you can reproduce it? If you have a small example from at least how does the structure with the mapper and the config looks like, it would be great :) |
@filiphr the real mappers are quite big. It happens when you have a shared config and non existing properties. The exact conditions I need to figure out... |
I had the same problem reported in issue #1278. I tried debugging "process" maven goal (thanks for this advice, it was fun). It has turned out that my problem is related with #1198 - the inheriting mapper is located in a different jar than the inherited mapper, so all parameter names in inheriting mapper are overriden with names arg0, arg1, arg2, arg3 ... As a consequence each mapping method with multiple input parameters was not correctly defined. I work with Java 6, so solution with preserving parameter names during compilation avaibale in Java 8 is not applicable for me. The only one option in to use arg0, arg1 ... as parameter names. Thanks for your help! |
@Alicja-Majewska glad that you think the debugging was fun 😄 . Yes having jars in a different jar is problematic when the parameter names are not preserved. |
It is related to the combination |
Closed via 6fbc4cf |
@filiphr : this time on a valid line 😄
The text was updated successfully, but these errors were encountered: