vladimirfx commented on issue #1197:
URL: https://github.com/apache/camel-quarkus/issues/1197#issuecomment-633006364
> camel-cdi is meant for when the Camel application is deployed into a full
CDI container (E.g Weld etc). There is currently no camel-quarkus extension for
it and its unlikely there ever will be because we provide CDI support via
integration with Quarkus Arc out of the box.
Actually it is my main question - how to DISABLE scanning of CDI beans for
Arc. It is not needed in this case. And many other cases I think. Current
situation is very strange - there is no CDI support but CDI beans from
dependencies completely broke Quarkus own DI. Very annoying...
> Also, I think the `TransactedPolicy` support in camel-cdi is dependent on
the `java:/TransactionManager` JNDI binding. This wont work on Quarkus since
there is no JNDI support.
It is a simplest part - trivial subclass on needed policy (may be inside
routes dentition class) can inject TransactionManager from Quarkus into
protected JtaTransactionPolicy.transactionManager .
Actually it is what I starter from. That approach is more explicit than all
that CDI magic.
Interestingly, `org.apache.camel.cdi.transaction` do not depend on CDI at
all (@Resource is not CDI only thing). It would be nice to extract this
implementation in its own module.
What do you think?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
