Eclipse Community Forums: Remote Application Platform (RAP)

Help

Home

Home » Eclipse Projects » Remote Application Platform (RAP) » Deprecation of PhaseListeners

Show: Today's Messages :: Show Polls :: Message Navigator

Deprecation of PhaseListeners [message #1406597]

Sun, 10 August 2014 14:58

Thomas Kratz

Messages: 165
Registered: July 2009

Senior Member

I rely in my selenium tests heavily on inserting information to the dom by a Phaselistener. Now it's been deprecated, and I guess it will be removed by 3.0.
Is there going to be a way to process the widgets in the tree in 3.0 other than PhaseListeners?

Regards
Thomas

Report message to a moderator

Re: Deprecation of PhaseListeners [message #1406826 is a reply to message #1406597]

Mon, 11 August 2014 07:46

Ivan Furnadjiev

Messages: 2339
Registered: July 2009
Location: Sofia, Bulgaria

Senior Member

Hi Thomas,
yes - PhaseListeners are deprecated and probably will be removed from
RAP 3.0. As a replacement (not completely) we implemented MessageFilter
- still internal, but we will make it API for 3.0 release. MassageFilter
could be added to ApplicationContext(Impl). It's similar to
ServletFilter and allows you to execute a code
(MessageFilter#handleMessage) for every request/response (with
incoming/outgoing protocol message as parameter). I'm not sure if the
new MessageFilter will be suitable for you - there is no access to
display (only to protocol message) and in case of SWT operational mode
(workbench) it is executed outside UI thread.
Best,
Ivan

--
Ivan Furnadjiev

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/

Report message to a moderator

Previous Topic:	How can i add Google Analytics?
Next Topic:	ClientScripting callback/messagebox

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat May 30 09:48:40 GMT 2020

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter