In general looks pretty good, not to many comments about it.

My only comments are the following:

Deploying as a Service processes and task as Services: Is the ESB going to be necessary?  Since we are going to be able to installed this on Jboss and other Application Servers that are capable of publishing service I don’t think is a great Idea to force the use of the jboss ESB.

I think is a mistake to continue using the web based editor, at least the you are using right know, it not very business user oriented, you should check other alternatives, take a look at many other vendor tools and you could get very good Ideas, I thing visual swimlanes for example is a most on every respectable bpm tool.

I really like that you are separating history repository from current work, that really helps performance, but have to be also able to plug the reporting tools to the current information in some way, probably not have out-of-the-reports with that but let the user or developer use this powerful tools with the ongoing processes.

I’ll wait to see what are you taking about when you say web-based console, faces? GWT? Seam? I think right know, looking at your architecture I see that you are working more on a complete suite and not only on a bpm engine as the past ones, the portal, console or what ever you want to call it becomes of great important when people comes to your tool and decides if adopt it or not.

Of course all of this is just opinion.

Regards,

Roberto