lburgazzoli edited a comment on pull request #2103:
URL: https://github.com/apache/camel-quarkus/pull/2103#issuecomment-758696381
@ppalaga
I've been thinking a little bit about this and one of the options could be
that we create a lightweight route builder that has some limitations, like it
does not provide a camel context:
| Type | Kind
|
|--------------------|--------------------------------------------------------------|
| RoutesBuilder | interface
|
| SimpleRouteBuilder | provide limited functionalities, no access to camel
context |
| RouteBuilder | same as today
|
Then camel-quarkus can safely inspect `SimpleRouteBuilder` at build time so
it is up to the user to consciously pick the builder that fits better. This may
also help cleaning up the `RouteBuilder` a bit. Also we can limit inspection to
classes that are no exposed to CDI so they should not have injection points.
I'm not convinced that giving to the user an option to know in which phase
the `configure()` method is invoke would be a good options as, IMHO, this
detail should no leak to the end user.
Another options would be to have some sort of proxy for some of the bits
such the camel context (similar to what @gnodet did for the "camel context
lite" to deal with build vs runtime properties) but I don't know how complex to
implement and maintain it would be.
----------------------------------------------------------------
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
