Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332111 - [BrowserFunction] Support Browser#execute inside BrowserFunction
Summary: [BrowserFunction] Support Browser#execute inside BrowserFunction
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.4 M4   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 330806
  Show dependency tree
 
Reported: 2010-12-08 05:37 EST by Ivan Furnadjiev CLA
Modified: 2010-12-10 03:08 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Furnadjiev CLA 2010-12-08 05:37:31 EST 
Currently, when Browser#execute is called inside the browser function, the result from the browser function is lost. This is true, because we expect to have a valid result in the same request that triggers the browser function. In case of Browser#execute inside the browser function, the result is delayed because Browser#execute stops its execution and wait to finish (intermediate request is issued).
Comment 1 Ivan Furnadjiev CLA 2010-12-10 03:08:55 EST 
Fixed in CVS HEAD. Now in case of Browser#execute inside a browser function, the "execute" sends synchronous request. Thus, RAP now behaves like in SWT in this case.