Request.js add some codes in RAP1.3 and UICallBackServiceHandler without any response [message #547303] |
Fri, 16 July 2010 09:13  |
Eclipse User |
|
|
|
Hi Ivan and all experts,
The RAP version I am using is RAP1.3.
I found that the file of "org\eclipse\swt\Request.js" in "org.eclipse.rap.rwt.q07_1.3.0.20100615-1704.jar" adds some codes below:
// [if] Dispose the last transport before creating the new one
// see bug 301261
if( this._lastTransport != null ) {
this._lastTransport.getRequest().dispose();
this._lastTransport.dispose();
}
When my rap application is running, I found that org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler without any response, the server side cannot push data to client automatically, so I need to use the mouse to click on UI interface each time to trigger a UI refresh.
I can reproduce this problem every time.
But when I delete these codes, it works fine, the UICallBackServiceHandler work normally.the client UI data received from the server side can automatically refresh.
Best Regards
|
|
|
|
|
Re: Request.js add some codes in RAP1.3 and UICallBackServiceHandler without any response [message #548236 is a reply to message #547303] |
Wed, 21 July 2010 08:13   |
Eclipse User |
|
|
|
If you think this is a bug, please file a bugzilla along with a
standalone example to reproduce the problem
Regards,
Rüdiger
On 16.07.2010 11:13, lyp wrote:
> Hi Ivan and all experts,
>
> The RAP version I am using is RAP1.3.
>
> I found that the file of "org\eclipse\swt\Request.js" in
> "org.eclipse.rap.rwt.q07_1.3.0.20100615-1704.jar" adds some codes below:
>
> // [if] Dispose the last transport before creating the new one
> // see bug 301261
> if( this._lastTransport != null ) {
> this._lastTransport.getRequest().dispose();
> this._lastTransport.dispose();
> }
>
> When my rap application is running, I found that
> org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler without any
> response, the server side cannot push data to client automatically, so I
> need to use the mouse to click on UI interface each time to trigger a UI
> refresh.
> I can reproduce this problem every time.
>
> But when I delete these codes, it works fine, the
> UICallBackServiceHandler work normally.the client UI data received from
> the server side can automatically refresh.
>
> Best Regards
|
|
|
Re: Request.js add some codes in RAP1.3 and UICallBackServiceHandler without any response [message #548413 is a reply to message #547303] |
Wed, 21 July 2010 17:48  |
Eclipse User |
|
|
|
Hi,
your right, these lines broke the UICallback when a KeyListener was used
at the same time. This problem has been reported in this bug:
317616: KeyListener breaks UICallback on IE, Chrome, Safari
https://bugs.eclipse.org/bugs/show_bug.cgi?id=317616
It is fixed in CVS HEAD, the fix will also be part of RAP 1.3.1.
Regards, Ralf
lyp wrote:
> Hi Ivan and all experts,
>
> The RAP version I am using is RAP1.3.
>
> I found that the file of "org\eclipse\swt\Request.js" in
> "org.eclipse.rap.rwt.q07_1.3.0.20100615-1704.jar" adds some codes below:
>
> // [if] Dispose the last transport before creating the new one
> // see bug 301261
> if( this._lastTransport != null ) {
> this._lastTransport.getRequest().dispose();
> this._lastTransport.dispose();
> }
>
> When my rap application is running, I found that
> org.eclipse.rwt.internal.lifecycle.UICallBackServiceHandler without any
> response, the server side cannot push data to client automatically, so I
> need to use the mouse to click on UI interface each time to trigger a UI
> refresh.
> I can reproduce this problem every time.
>
> But when I delete these codes, it works fine, the
> UICallBackServiceHandler work normally.the client UI data received from
> the server side can automatically refresh.
>
> Best Regards
|
|
|
Powered by
FUDForum. Page generated in 0.03242 seconds