# Autowire in Java Client 8.10

**URL:** <https://forum.camunda.io/t/autowire-in-java-client-8-10/69123>\
**Category:** Camunda 8 Topics\
**Tags:** spring-boot-starter\
**Created:** [October 16, 2026, 7:30am UTC](https://forum.camunda.io/t/autowire-in-java-client-8-10/69123 "2026-10-16T07:30:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hakanostrom](https://forum.camunda.io/user_avatar/forum.camunda.io/hakanostrom/32/22777_2.png) [@hakanostrom](https://forum.camunda.io/u/hakanostrom)\
**Post date:** [October 16, 2026, 7:30am UTC](https://forum.camunda.io/t/autowire-in-java-client-8-10/69123/1 "2026-10-16T07:30:27Z")

</div>

I am getting a strange oddity in IntelliJ (2026.2.3 using Gradle) when switching to camunda 8.10.3 java client (from 8.9.23).

Al of a sudden the autowire (or constructor) injection gets an IntelliJ-warning. The compilation works but a red squiggly line appears saying " Could not autowire. No beans of ‘CamundaClient’ type found.". I use plain constructor injection in my service, like so:  
`public CamundaService(CamundaClient camundaClient) {`  
` this.camundaClient = camundaClient;`  
`}`

---

<div class="post-metadata">

**Author:** ![zee-bot](https://forum.camunda.io/user_avatar/forum.camunda.io/zee-bot/32/32886_2.png) [@zee-bot](https://forum.camunda.io/u/zee-bot)\
**Post date:** [October 16, 2026, 7:31am UTC](https://forum.camunda.io/t/autowire-in-java-client-8-10/69123/2 "2026-10-16T07:31:52Z")

</div>

The IntelliJ `CamundaClient` autowire warning after upgrading to 8.10 is likely related to key changes in how the Spring Boot Starter is packaged and configured in that version. I found the following relevant resources:

- [Camunda 8.10 Migration Guide – Upgrade Steps](https://docs.camunda.io/docs/apis-tools/migration-manuals/migrate-to-810/#upgrade-steps)
- [Camunda Spring Boot Starter – Version Compatibility (Spring Boot 3 vs 4)](https://docs.camunda.io/docs/apis-tools/camunda-spring-boot-starter/getting-started/#version-compatibility)
- [Migrate to the Camunda Spring Boot Starter](https://docs.camunda.io/docs/apis-tools/migration-manuals/migrate-to-camunda-spring-boot-starter/)
- [Camunda Spring Boot Starter – Getting Started](https://docs.camunda.io/docs/apis-tools/camunda-spring-boot-starter/getting-started/)

Does this help? If not, can anyone from the **community** jump in? 👋

* * *

💡 _Hints: Use the **Ask AI** feature in [Camunda’s documentation](https://docs.camunda.io/) to chat with AI and get fast help. **Report** bugs and features in [Camuda’s GitHub issue tracker](https://github.com/camunda/camunda/issues/new/choose). Trust the process._ 🤖

---

<div class="post-metadata">

**Author:** ![rachelwilson](https://forum.camunda.io/letter_avatar_proxy/v4/letter/r/8edcca/32.png) [@rachelwilson](https://forum.camunda.io/u/rachelwilson)\
**Post date:** [November 2, 2026, 6:58am UTC](https://forum.camunda.io/t/autowire-in-java-client-8-10/69123/3 "2026-11-02T06:58:36Z")

</div>

if it compiles and the app actually starts and injects, id treat this as intellij not seeing the auto config rather than a real missing bean. after a version bump that happens when gradle still has a mix, like the old starter sitting next to the new client, so check the dependency tree for both versions and do a full gradle reimport. if only one version shows up, invalidate caches and restart usually makes the red squiggle catch up.

---

<div class="post-metadata">

**Author:** ![hamzaBraimi](https://forum.camunda.io/user_avatar/forum.camunda.io/hamzabraimi/32/33744_2.png) [@hamzaBraimi](https://forum.camunda.io/u/hamzaBraimi)\
**Post date:** [November 2, 2026, 10:49am UTC](https://forum.camunda.io/t/autowire-in-java-client-8-10/69123/4 "2026-11-02T10:49:02Z")

</div>

IntelliJ-only warning, not a real bug. Two quick checks:

1. **Run the app.** If `CamundaClient` injects fine, it’s cosmetic. If it fails at startup, make sure `camunda-spring-boot-starter` (not just `camunda-client-java`) is on the classpath.

2. **If it works, fix the IDE.** Try File → Invalidate Caches and Restart, then reimport the Gradle project. If the squiggle stays, add `@SuppressWarnings("SpringJavaInjectionPointsAutowiringInspection")` on the constructor.
