DefaultProcessDiagramGenerator nullpointer
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2014 01:52 AM
In Activiti 5.16.1 i get the following ugly "warning" exception when deploying my activie proces, usin spring.
Diving into the code it was easy to see that i just needed to set the "createDiagramOnDeploy" property to false on my ProcessEngineConfiguration. This is set default to true, but then this also gives an exception by default.
Just thought this was a bit ugly.
Default behaviour printing stacktraces like that.
Regards
java.lang.NullPointerException: null at org.activiti.image.impl.DefaultProcessDiagramGenerator.connectionPerfectionizer(DefaultProcessDiagramGenerator.java:593) ~[activiti-image-generator-5.16.1.jar:5.16.1] at org.activiti.image.impl.DefaultProcessDiagramGenerator$22.draw(DefaultProcessDiagramGenerator.java:358) ~[activiti-image-generator-5.16.1.jar:5.16.1] at org.activiti.image.impl.DefaultProcessDiagramGenerator.drawArtifact(DefaultProcessDiagramGenerator.java:680) ~[activiti-image-generator-5.16.1.jar:5.16.1]
Diving into the code it was easy to see that i just needed to set the "createDiagramOnDeploy" property to false on my ProcessEngineConfiguration. This is set default to true, but then this also gives an exception by default.
Just thought this was a bit ugly.
Default behaviour printing stacktraces like that.
Regards
Labels:
- Labels:
-
Archive
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2014 06:14 AM
How does your process xml looks like? Cause you should only see this exception if your BPMN 2.0 xml has diagram info, but NOT for a certain sequenceflow (which leads to the NPE). In theory, if you used a BPMN 2.0 visual tool, this shouldn't happen.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2014 09:05 AM
The xml contains diagram info.
Created with the activiti plugin.
Created with the activiti plugin.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2014 06:59 AM
Hmm damn, sounds like a bug. Any chance you could post your xml here?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2014 09:15 AM
Unfortunately no. Confidential company stuff.
I tried to create a seperate proces that recreated the issues but to no avail. It occurs with 70 percent of the processes. The processes all are connected through events however. Possibly thatis the reason why the standalone test proces succeeds. Anyhow, no biggie, it is just a warning and i was able to disable it.
I tried to create a seperate proces that recreated the issues but to no avail. It occurs with 70 percent of the processes. The processes all are connected through events however. Possibly thatis the reason why the standalone test proces succeeds. Anyhow, no biggie, it is just a warning and i was able to disable it.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2014 12:32 AM
The exception will happen in case of a flow without a source element, which shouldn't be possible with a correct BPMN XML I think. Could you debug which flow is the source of this exception and why it doesn't have a source element?
Best regards,
Best regards,
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2014 07:38 AM
When i've got some time to spare i will. At the moment ir's not a problem antmore because i disabled it

