Added a patched XmlHttPProxy

[heiko.braun]

Forgot to mention that it allows you to bypass the same origin policy as well.

[michaelneale]

So what does this give that normal hosted mode with -noserver flag doesn't do? (it also doesn't seem to be using GWT's "native" RPC mechanism).

[heiko.braun]

Well, depends on how you test. "-noserver" requires you to deploy the console to an external container, right? Given the server side is deployed (in my case console and server are different modules) then you can simply work in hosted without redeployment of the console.

[michaelneale]

well how does that work? you still have to have a jboss instance running right?

Also - does this not use GWT RPC?

[heiko.braun]

Yes, there is a JBoss instance that hosts the console server component. It uses REST/Json to integrate with GWT.

GWT -> REST -> JBPM

In order to decouple the server part from the client (i.e. in hosted mode)
you need to bypass the same origin policy. Thus the proxy, which is currently only used when running in hosted mode.

The nice thing is that you can stay in hosted mode, not worrying about server resources (datasources, etc) with the server component deployed on JBoss. It reduces the turnaround times a lot.