You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2021/08/19 12:58:51 UTC

[GitHub] [camel-quarkus] ppalaga commented on pull request #3019: CoreTest.testCamelContextAwareRegistryBeansInitialized failing after …

ppalaga commented on pull request #3019:
URL: https://github.com/apache/camel-quarkus/pull/3019#issuecomment-901893397


   > It's not clear to me whether we're just masking an actual issue here. If I search for CamelContextAware beans, then I'd expect the CamelContext to not be null.
   
   Yeah, when thinking of it again, I am getting the same impression. On one hand user beans are their responsibility but OTOH the same holds for our RouteBuilders. We should better set `@ApplicationScoped` on them so that ppl. do not copy it from us. And once we do it, we can actually get back to querying the whole registry. Let me do it like that.


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org