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

> I just a found an interesting part in engine.js:
>
>  /** These URLs can be configured from the server */
> 252 dwr.engine._ModePlainCall = "/call/plaincall/";
> 253 dwr.engine._ModePlainPoll = "/call/plainpoll/";
> 254 dwr.engine._ModeHtmlCall = "/call/htmlcall/";
> 255 dwr.engine._ModeHtmlPoll = "/call/htmlpoll/";
>
> How can theses URLs be configured from the server? Setting them to the
> absolute URL should solve my problem.
>
>
>
>
> Jochen Huber wrote:
>  
>> I've tried to manipulate both dwr.engine._defaultPath and
>> dwr.engine._pathToDwrServlet. Well, guess what: variables are set
>> correctly (checked it with Firebug) but without any effect.
>>
>> Due to the false post request, I'm not able to execute any DWR scripts.
>> I'll have to switch back to 2.0.5 which leads me to my old problem of not
>> being able to transfer DOM objects properly. :(
>>
>>
>> David Marginian-2 wrote:
>>    
>>> 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.
>>>
>>>      
>
>