We hook the notification handler for the imixs ImedeateCatchEvent now in the RuntimeExtension during the Lifecycle Event 'BUSINESS_OBJECT_CREATED'.
The problem here is that in that point we can not identify the business object clearly because not custom attributes are yet attaged to the object.
In contrast the Event 'BUSINESS_OBJECT_INITIALZED' is not fired during loading the bpmn file the first time. This is an issue which mybe fixed in future release. If so, we can test the business object in more details to the Imixs target namespace. This will allow to remove this check from the Notifiyer method in the eventAdater itself!
We hook the notification handler for the imixs ImedeateCatchEvent now in the RuntimeExtension during the Lifecycle Event 'BUSINESS_OBJECT_CREATED'. The problem here is that in that point we can not identify the business object clearly because not custom attributes are yet attaged to the object. In contrast the Event 'BUSINESS_OBJECT_INITIALZED' is not fired during loading the bpmn file the first time. This is an issue which mybe fixed in future release. If so, we can test the business object in more details to the Imixs target namespace. This will allow to remove this check from the Notifiyer method in the eventAdater itself!
But currently this seems not to be critical.