DWR 3 M1: dwr/call/plaincall/__System.pageLoaded.dwr on "wrong" port/server

Hello,

in my current setup, I'm _required_ to have a different server than my application server serve HTML files. Let's say web-pages are being served from an Apache on IP A and DWR runs on a Tomcat on IP B.

What I usually did with DWR2 was to include <script> references to engine.js on IP B (and other classes, respectively) within web-pages served from the Apache on IP A. This worked out perfectly alright.

Let's say an Apache runs on 127.0.0.1 Port 8000. A Tomcat, serving the dwr scripts, runs on 127.0.0.1 Port 8080. Thus I would include

<script type='text/javascript' src='http://127.0.0.1:8080/web/dwr/interface/CollaborationManager.js'></script>

in web-pages served from the web-server. As a matter of fact (with DWR 3 M1) this results in the following post request

POST http://127.0.0.1:8000/web/dwr/call/plaincall/__System.pageLoaded.dwr

which fails due to the fact of DWR being located on 127.0.0.1:8080, not on 8000. Consequently, DWR scripts cannot be executed.

Any ideas would be appreciated :)