« Return to Thread: DWR 3 M1: dwr/call/plaincall/__System.pageLoaded.dwr on "wrong" port/server
Re: DWR 3 M1: dwr/call/plaincall/__System.pa
by David Marginian-2
::
Rate this Message:
Bummer, you're welcome too bad I haven't been very helpful.
DefaultRemoter has a method called getPathToDwrServlet. It uses the
information from the request to construct a path to the dwr servlet.
This path is injected into the generated engine.js as
dwr.engine._pathToDwrServlet which is why you are seeing the port being
replaced. I know other people have overrode the
dwr.engine._pathToDwrServlet variable successfully (although kind of a
hack).
Try something like:
dwr.engine._pathToDwrServlet = "whatever it should be";
Hope this helps.
Jochen Huber wrote:
> David,
>
> thank you very much for your really fast answers throughout the day. :)
>
> Unfortunately I cannot forward the requests from apache to tomcat. I cannot
> manipulate/re-configure the web server :(
>
>
>
> David Marginian-2 wrote:
>
>> There are numerous ways to forward requests from apache to tomcat. I
>> recommend taking a look on the web. Here is an example:
>> http://rimuhosting.com/mod_jk2_and_mod_proxy_ajp.jsp
>>
>> Jochen Huber wrote:
>>
>>> 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 :)
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
DefaultRemoter has a method called getPathToDwrServlet. It uses the
information from the request to construct a path to the dwr servlet.
This path is injected into the generated engine.js as
dwr.engine._pathToDwrServlet which is why you are seeing the port being
replaced. I know other people have overrode the
dwr.engine._pathToDwrServlet variable successfully (although kind of a
hack).
Try something like:
dwr.engine._pathToDwrServlet = "whatever it should be";
Hope this helps.
Jochen Huber wrote:
> David,
>
> thank you very much for your really fast answers throughout the day. :)
>
> Unfortunately I cannot forward the requests from apache to tomcat. I cannot
> manipulate/re-configure the web server :(
>
>
>
> David Marginian-2 wrote:
>
>> There are numerous ways to forward requests from apache to tomcat. I
>> recommend taking a look on the web. Here is an example:
>> http://rimuhosting.com/mod_jk2_and_mod_proxy_ajp.jsp
>>
>> Jochen Huber wrote:
>>
>>> 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 :)
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...
« Return to Thread: DWR 3 M1: dwr/call/plaincall/__System.pageLoaded.dwr on "wrong" port/server
| Free embeddable forum powered by Nabble | Forum Help |
