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
Jdbc-derby: missing resource in native mode #22058
Comments
I forgot to mention that problem is not happening with dev services. |
Could you give #22059 a try please? |
I'll try it. |
To be clear, I don't think we expect Derby to work in native; I see you only need the client here, so that might be doable but this wasn't expected to work, nor tested. |
Right, but I do see we some reflection registration already in there, so if the fix is as simple as #22059, then I see no reason not to add it :) |
Sure ok I have no problem with someone wanting to fix it :) |
👍🏼 |
@geoand I tried your fix and it fixes the problem with missing resources.
I'll investigate it more to find from what is causing the problem It could be quarkus or the test itself. |
Register derby resource bundler in native mode
Fixes: quarkusio#22058 (cherry picked from commit 8e99b5d)
Fixes: quarkusio#22058 (cherry picked from commit 8e99b5d)
Describe the bug
I'm fixing camel-quarkus integration test of sql extension. If I use external derby database (using docker) for the test, I got an exception in native mode:
Problems seems to be similar as #21639
Expected behavior
Jdbc derby should work i native mode without an error.
Actual behavior
No response
How to Reproduce?
As a reproducer, please use integration-tests/sql from my branch: https://github.com/JiriOndrusek/camel-quarkus/tree/3260-sql-derby-quarkus-master-reproducer
(property
SQL_USE_DERBY_PORT
just tells docker which port to use, so use for example 1527 - but it could be any random free port number)3. Run test with a property for derby
mvn clean verify -Pnative -f integration-tests/sql -Dcq.sqlJdbcKind=derby
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
Current failure was simulated on quarkus built from main branch (revision 32773ed)
The same exception happens also with quarkus 2.5.0.
The text was updated successfully, but these errors were encountered: