Problems with change in ConstructorInstantiator

[camunda]

Hi Alex.

I updated to your latest changes locally and have a problem with the change in ConstructorInstantiator. The new version throws a NullPointerException if you specify "constructor" configuration without a configuration. This may make sense, but in the current ESB integration the "org.jboss.soa.esb.services.jbpm.cmd.AsyncProcessSignal$AsyncSignalAction" is created as "constructor-configured" but with "configuration" null.

So after updating to the new version every started process instance within the ESB environment fails with a NPE. So in the sense of not breaking compatibility I would propose to add the behavior as before the change to the new code, means: If configuration is null, type is assumed to be String and value is null.

Got what I mean. D'accord?

Then I can commit it...

Cheers
Bernd

[camunda]

To not forget it I already committed a test case for this behavior which currently fails...

[aguizar]

Hi Bernd. Thank you for spotting this. Fortunately the refactoring is fairly recent and no compatibility has been broken in any released version. I'll go ahead and fix it.

[camunda]

Cool, thanks.