Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345424 - Replace uses of updateListener mechanism in JSWriter
Summary: Replace uses of updateListener mechanism in JSWriter
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.4   Edit
Hardware: All iOS
: P3 enhancement (vote)
Target Milestone: 1.5 M1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-11 09:51 EDT by Ralf Sternberg CLA
Modified: 2011-06-22 08:25 EDT (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 Ralf Sternberg CLA 2011-05-11 09:51:35 EDT 
The JSWriter has a mechanism that directly connects client event handler functions with client events from the server side. This violates the separation of client and server and is not compatible with the new protocol (bug 311355).

The event wiring should now be done completely on the client. The server only needs to inform the client whether a listener is attached to a widget by synchronizing a "hasXxxListener" property.

In preparation of the protocol, we should rework those places that still use the old mechanism. This involves calls to these methods:
* JSWriter#addListener( ... )
* JSWriter#removeListener( ... )
* JSWriter#updateListener( ... )

and uses of these classes:
* JSListenerInfo
* JSListenerType

Since these methods and classes are public API, they should be kept functional and tested, but marked as deprecated and removed later.
Comment 1 Ivan Furnadjiev CLA 2011-06-22 08:25:53 EDT 
These methods:

  •  JSWriter#addListener( ... )
	•  JSWriter#removeListener( ... )
	•  JSWriter#updateListener( ... )

and classes:

	•  JSListenerInfo
	•  JSListenerType
	
are no longer used in RWT and forms.