Re: [I] Defer CamelRuntime start until after test setup is completed [camel-quarkus]

2025-05-20 Thread via GitHub


jamesnetherton closed issue #7291: Defer CamelRuntime start until after test 
setup is completed
URL: https://github.com/apache/camel-quarkus/issues/7291


-- 
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-unsubscr...@camel.apache.org

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



Re: [I] Defer CamelRuntime start until after test setup is completed [camel-quarkus]

2025-05-20 Thread via GitHub


jamesnetherton commented on issue #7291:
URL: https://github.com/apache/camel-quarkus/issues/7291#issuecomment-2894403786

   Not much we can do for this. Since the `CamelContext` is effectively a 
singleton.
   
   When it's started for one test, then obviously it's started for all of them.
   
   Fixing this would require a test class scoped `CamelContext` instance. Which 
currently isn't really possible without all tests having their own 
`QuarkusTestProfile` to force a 'clean' app restart.
   
   Probably what we really need is something akin to Spring `@DirtiesContext` 
https://github.com/quarkusio/quarkus/issues/26818.


-- 
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-unsubscr...@camel.apache.org

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