Replies: 1 comment
-
The problem seems to be that both are called during startup, I assume only one should be used. The XML version uses my configuration and is correctly configured. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I am just getting started with Quarkus and I wonder if there are any best practices about troubleshooting issues with the generated classes such as ApplicationImpl? I can usually find the root of any issue with a new framework by stepping through the code, but this doesn't work here...
I am using maven & IntelliJ, and a simply 2-module project ("core"for stuff I intend to reuse and "application"). In the application module I have declared the quarkiverse quarkus-mybatis extension which I use for DB access.
My issue is that Quarkus creates two MyBatis configurations and SQL session factories; one of them is properly set up with the mybatis properties I have defined in application.properties, the other one is not.
The stack traces are below, they come straight from ApplicationImpl.... and I can't easily look into that code?
Regarding the problem itself, is it ok to / am I supposed to declare the quarkiverse dependency in both modules? Or should it appear in the applicatoin module only, and would that explain the problem? I need the MyBatis annotations in the library module, but I could get them from the lower-level mybatis dependencies if needed.
Thanks!
Stack trace #1
Stack trace #2:
Beta Was this translation helpful? Give feedback.
All reactions