I just verified that adding a new process in Guvnor should show up in the console.
Just a few things to be aware of:
* Make sure to have the defaultPackage built successfully before opening the jbpm-console the first time (otherwise it will fail to set up Guvnor synchronization)
* After adding a new process to Guvnor defaultPackage, don't forget to rebuild the package (as this makes the changes available to knowledge bases out there). There's also a small delay (configured to 10s I think) in between the building of the package and the updating of the knowledge base.
After doing this, simply refreshing your process list should make the new process show up.
Let me know if this helps or not.
I have been having the same problem. I think itis because
the ChangeSet.xml in jBPM5/jbpm-installer/lib/jbpm-5.1.0.Final-gwt-console/jbpm-gwt-console-server-5.1.0.Final/WEB-INF/lib/jbpm-gwt-graph-5.1.0.Final has<change-set xmlns='http://drools.org/drools-5.0/change-set'
<resource source='http://localhost:8080/drools-guvnor/org.drools.guvnor.Guvnor/package/default/LATEST' type='PKG' />
default needs to be defaultPackage. I plan to change this value and re-jar things and re-test next week.
That file indeed seems to be pointing incorrectly to default instead of defaultPackage (and I have corrected this). This does not seem to be the cause though, as he seems to be able to see processes deployed to guvnor in the console, just not updates when the package on guvnor is rebuild (I think that the ChangeSet in jbpm-gwt-core is taking precendence on the classpath, so the incorrect one in jbpm-gwt-graph is ignored).
@Jeff: The following sequence should work out-of-the-box: upload process to defaultPackage in guvnor, open guvnor and rebuild defaultPackage, open up jbpm-console and check if the process shows up
I followed exactly what in the 5.1 user guid. Actually I did the same while in 5.0. Now it appears to me that the first problem disappeared. I guess it was due to some delay in my local env. But the second problem is still there. I first archived a process, rebuilt the defaultPackage, and kept refreshing in the web console, the process didn't disappear. Then I deleted the process from Guvnor from the archive list, and rebuilt the defaultPackage again. The process was still in the console, no matter how hard I refreshed.