Repository navigation
Replies: 1 comment 7 replies
|
Any new progress? I'm facing the same issue and can't access the datasources as shown in |
|
Thanks much, that worked great for me. I created import io.agroal.api.AgroalDataSource;
import io.quarkus.agroal.DataSource;
import io.quarkus.agroal.runtime.DataSources;
import io.quarkus.arc.Arc;
import java.lang.annotation.Annotation;
...
public void someFunction(...) {
agroalDataSource = Arc.container().instance(DataSources.class, new Annotation[0]).get().getDataSource("myname");
conn = agroalDataSource.getConnection();
// Now use the connection like any other JDBC connection
// ...
}The hardest part was probably finding just the right stuff to import :) |
|
Hey eggyknap Great, that its working for you as well. |
|
That's considerably cleaner, thanks. Now, however, I get errors that my connection is already closed, when the enclosing JTA system tries to commit the transaction. This is the latest in a long series of disappointments trying to get this to work; for now I'm going back to our old, soon-to-be-unsupported authentication method, because I've got to get other stuff done than just messing around with Keycloak |
|
Hi, as a reference: I did not use Agoral data source, as that requires an extra import. I used this one session.getProvider(JpaConnectionProvider.class).getEntityManager(); where the session is the KeycloakSession object in the constructor. and then this.query = this.em.createNamedQuery("QUERY_NAME", YOUREntity.class); Hope this helps |
|
Hey Joshua Maybe something to try once you have a little time to experiment. The solution from Simin works as well but only to get a connection the same database that keycloak is using for its own data imho |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
I have a provider that should be migrated from JBOSS distribution to Quarkus distribution.
In the JBOSS distribution I was leveraging the JNDI datasource, while this is becoming vague in the quarkus distribution.
In quarkus.properties I have
`
quarkus.datasource.db-kind=oracle
quarkus.datasource.jdbc.url=VALIDURL
quarkus.datasource.username=VALIDUSERNAME
quarkus.datasource.password=VALIDPASSWORD
quarkus.datasource.jdbc.max-size=13
`
In build.gradle I have
`
`
In provider factory I have
`
`
However on datasource.getConnection() I get
`
`
Does anyone has idea here how should the datasources used correctly?
All reactions