+++ This bug was initially created as a clone of Bug #1317665 +++

Description of problem:

If users open a process model, a new entry in his inbox/recentViewed XML file will be added referencing a "dummy" repository, that does not actually exist.

This will break the Project Explorer, since I will not be able to open any process definition anymore.

Version-Release number of selected component (if applicable):

How reproducible:
Always

Steps to Reproduce:
0. This issue was reproduced using BPM Suite 6.2.1
1. Create a project that has a simple process and deploy it
2. Go to process management and start a new instance
3. Go to process instances and see the process model

Actual results:

An entry will be added to user inbox referencing a dummy repository and when trying to open a new process definition in process explorer, it will not be opened.

Expected results:

No dummy entry in inbox/recentViewed

Additional info:

The following video shows this issue:

https://drive.google.com/a/redhat.com/file/d/0B3wF6UICl7kseDVMMnp2Y0ZsU3M/view?usp=sharing

The problem seems that when we open the process model, an event of type ResourceOpenedEvent is being fired somewhere. You can configure debugging and add a break point in the following method from class InboxBackendImpl

public void recordOpeningEvent( @Observes final ResourceOpenedEvent event )

You will see that something will fire this event and add the dummy url of the process model to the list of recentViewed files.

When you try to open a new process definition it also tries to load the recentViewed list to add the file you just opened to it, and then you have an exception(turn on errai debug to see the exception), since the Dummy process does not exist. The exception is threw at uberfire level, when checking the resource URL:

Line 740 in class JGitFileSystemProvider:
--------------
public Path getPath( final URI uri )
throws IllegalArgumentException, FileSystemNotFoundException, SecurityException {
/// ....
if ( fileSystem == null )

// ....
}
--------------

— Additional comment from Alessandro Lazarotti on 2016-03-14 15:47:11 EDT —

asking for blocker flag as
such problem breaks the Project Explorer.

— Additional comment from JBoss Product and Program Management on 2016-03-14 15:50:08 EDT —

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.