Yes was a very fine answer and it filled with me with hope. I really want to leverage the
restful apiprovided by the console server. But things aren't so simple.
Now it seems obvious that the console server needs access to the spring context. Trying
to enumerate a list of deployed processes via the restful api in the deault jboss
integration causes all kinds of errors related to not finding the spring refrences in the
process definition files.
So it seems that there are two paths forward:
I can try to integrate a springified instance of jbpm application server with jboss.
Fooling around with the jbpm-service.sar
Or assuming my jpbm application is deployed as a war, I can try to expose the context to
gwt-console-server.war, perhaps by changing gwt-console-server-integration.jar.
I know there are also class loading issues, but I think those are all surmountable.
I think getting a springified version of jpbm integrated with the console server would eb
tremendously useful integration. I'm sure I could pull it off with a little guidance.
I would be happy to write up the solution and share it with others.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245881#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...