`NullPointerException`: Cannot invoke `IProgressMonitor.beginTask(String, int)` because `monitor` is null

[hangum]

`NullPointerException`: Cannot invoke `IProgressMonitor.beginTask(String, int)` because `monitor` is null

[ifurnadjiev]

Fixed in RAP 3.29 by using the latest platform bundle with the fix.

[hangum]

I modified the runtime to rap-3.22.0-R-20220906-0913 and it works fine.
I'll share a test site when I'm done with my busy work.

Thanks.

[mknauer]

Thank you for your report!
Since you mention a "modified runtime" in your last comment: Can you share with us what you have changed, or even better, create a pull request?

[dogla]

We may have stumbled across the same problem: monitor == null.
Unfortunately, we don't have a minimal standalone example to reproduce the problem.
I suspect the problem is due to the following commit in the eclipse platform:
eclipse-platform/eclipse.platform@9c3525c

Previously, a NullProgressMonitor was used in the platform if a ProgressProvider returned null.
In RAP, at least in our case, the RAP-specific org.eclipse.rap.ui.internal.progress.JobManagerAdapter is called, which returns null under certain conditions.
At first glance, RAP behaves as before, only the eclipse platform now handles null results differently, which leads to these subsequent errors.

A quick fix could be to add the NullProgressMonitor fallback handling to the RAP specific JobManagerAdapter.

[dogla]

See eclipse-platform/eclipse.platform#1282

[hangum]

@ifurnadjiev Thanks