Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 332111

Summary: [BrowserFunction] Support Browser#execute inside BrowserFunction
Product: [RT] RAP Reporter: Ivan Furnadjiev <ivan>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: 1.4   
Target Milestone: 1.4 M4   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on:    
Bug Blocks: 330806    

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.