This does make sense to me. One thing we can definitely do is the identity management console. User profile, account management, role-based-authorization etc, obviously we do not want to do it twice both in jBPM and Guvnor.
It is likely that the SOA Repository - Guvnor will be using a structure based on GWT+REST(Atom/Pub), not sure if this will be the case for jBPM. Of course we just started to look into this kind of architecture, we still need some time to prove that this architecture does work.
REST is fine. we already leverage that in the current console, even though it's plain json. But working on atompub shouldn't be a problem.
Regarding the common console components: I think that should be covered by the jboss console framework that mike brock is leading.
afaict, guvnor combines a GWT app pluggability mechanism and the business view upon an aggregated repository.
if this is correct...
would it be possible to extract the GWT app pluggability out of guvnor as something separate ?
the jBPM distribution could use the app-pluggability to combine the jBPM console with the (TBD) identity console.
and then the same pluggability can be used to pile it all together in guvnor later on.
does this make sense ?
Mike Brock is working on this as we speak.