I don't know the exact reasons but a lot of improvements have been made
in 3.0. Obviously, the cross-domain feature is there for security
purposes but it can be configured:
http://directwebremoting.org/dwr/server/servlet.
The bottom-line is that what you are doing is far from a typical use
case. Most users would configure apache to forward the requests to
tomcat and be done with it (no DWR changes necessary).
There may be a better way to accomplish what you need but we'll have to
wait for someone on the list who knows more than me.
Jochen Huber wrote:
> Thanks,
>
> I cached engine.js and changed the paths in this file directly. It does work
> as long as both servers run on the same IP. When the IP differs, I get a
> cross-domain exception. Nevertheless, including DWR scripts located on a
> different server worked in DWR 2.0.x.
>
> So here's my (final) question: Why has the code been changed? ;)
>
>
> David Marginian-2 wrote:
>
>> They are in a config file called defaults.properties.
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
