[
https://issues.apache.org/jira/browse/CAMEL-21115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Berman updated CAMEL-21115:
----------------------------------
Description:
I have a custom unit test which requires access to Camel context. My code is as
simple as:
{{@QuarkusTest
public class MyCustomTest {
@Inject
protected CamelContext camelContext;}}
It worked just fine prior to upgrading to Camel 4.7.0 and Quarkus 3.13.0 but
now I'm getting error:{{ java.lang.NullPointerException: Cannot invoke
"org.apache.camel.CamelContext.getCamelContextExtension()" because
"camelContext" is null}} and running the code in the debug mode confirms that
the camelContext is indeed null. Is it a known bug?
was:
I have a custom unit test which requires access to Camel context. My code is as
simple as:
```
@QuarkusTest
public class MyCustomTest {
@Inject
protected CamelContext camelContext;
```
It worked just fine prior to upgrading to Camel 4.7.0 and Quarkus 3.13.0 but
now I'm getting error: `java.lang.NullPointerException: Cannot invoke
"org.apache.camel.CamelContext.getCamelContextExtension()" because
"camelContext" is null` and running the code in the debug mode confirms that
the camelContext is indeed null. Is it a known bug?
> CamelContext is not injected
> ----------------------------
>
> Key: CAMEL-21115
> URL: https://issues.apache.org/jira/browse/CAMEL-21115
> Project: Camel
> Issue Type: Bug
> Components: camel-quarkus
> Affects Versions: 4.7.0
> Reporter: Eugene Berman
> Priority: Major
>
> I have a custom unit test which requires access to Camel context. My code is
> as simple as:
> {{@QuarkusTest
> public class MyCustomTest {
> @Inject
> protected CamelContext camelContext;}}
> It worked just fine prior to upgrading to Camel 4.7.0 and Quarkus 3.13.0 but
> now I'm getting error:{{ java.lang.NullPointerException: Cannot invoke
> "org.apache.camel.CamelContext.getCamelContextExtension()" because
> "camelContext" is null}} and running the code in the debug mode confirms that
> the camelContext is indeed null. Is it a known bug?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
