-
Notifications
You must be signed in to change notification settings - Fork 4
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
Unsatisfied dependency for type javax.persistence.EntityManager in orders-and-customers module #1
Comments
Please provide more explanation including commit |
Chris, as I wrote in the email, I need some time to prepare commit. Explanation: |
https://quarkus.io/guides/cdi-reference says:
|
Yes, jandex creates index automatically. Probably I can create index manually, but I am not sure that is better than adding jandex plugin to orders-and-customers in original sagas project. To summarize, we have following options:
I would prefer the first option. If you prefer 3 option, please confirm. |
My interpretation of this sentence is that eventuate-tram-sagas/orders-and-customers is a dependency of eventuate-tram-sagas-quarkus. You could therefore index eventuate-tram-sagas/orders-and-customers by adding the necessary entries to eventuate-tram-sagas-quarkus's application.properties. |
I indexed orders-and-customers by adding this:
to application.properties. But there is one thing. We have following dependency chain: orders-and-customers (original saga) -> orders-and-customers-quarkus -> orders-and-customers-quarkus-integration-tests To solve the issue, I needed to specify properties in both modules. Otherwise, if specify only in one place, no matter which one, the error appears. |
Everything is configured as in eventuate-tram-quarkus-examples-customers-and-orders.
However when I am trying to use EntityManager I am getting this:
Found this: quarkusio/quarkus#11483
I realized that entities are in eventutate-tram-sagas and not indexed by jandex.
Solved by copying orders-and-customers to eventuate-tram-sagas-quarkus
The text was updated successfully, but these errors were encountered: