ApplicationContext destroyed when setting ProcessVariable on bean initialization

[LinusHojaGER]

Environment

• OS: Linux, Windows
• Camunda Version: 7.19.13-ee
• Spring Boot Version: 2.7.15
• Spring Camunda Version: 1.0.6-camunda-7-19

Description

If create a Class extending ProcessVariable, calling super() in the constructor and setting the Variable Value right after the super() call by using set(VALUE), the ApplicationContext isnt working afterwards. For every call to the ApplicationContext, a NPE is thrown.

Steps to reproduce

1. Create a Class extending ProcessVariable
2. Call super() in the overridden Constructor
3. Call set(0) rigth after the super() call
4. Try to startup the Application

Observed Behavior

On every (also implicit) call to the ApplicationContext, e.g. bean initialization, a NullPointerException is thrown. The ApplicationContext is unusable.

Expected behavior

A more thought thru ErrorHandling should be implemented to

1. prevent camunda from crashing the whole Spring ApplicationContext
2. give the user a more describing error, why this is not working.

Root Cause (Required on prioritization)

Solution Ideas

Hints

Links

Breakdown

### Pull Requests

Dev2QA handover

• [ ] Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

[LinusHojaGER]

I just noticed that we are using wrapper classes that induce this behavior. No Issue from camunda as i can see so far.