Interface and Description |
---|
org.eclipse.rap.rwt.service.IApplicationStore
Use
ApplicationContext instead. |
org.eclipse.rap.rwt.theme.IControlThemeAdapter
Use ControlThemeAdapter instead.
|
org.eclipse.rap.rwt.application.IEntryPoint
use
EntryPoint instead |
org.eclipse.rap.rwt.application.IEntryPointFactory
Use
EntryPointFactory instead |
org.eclipse.rap.rwt.lifecycle.ILifeCycle
As of 2.0, PhaseListeners should only be registered in an
ApplicationConfiguration . For new applications and custom widgets, consider
the (still internal) RemoteObject API which is going to replace
PhaseListener. |
org.eclipse.rap.rwt.service.IResourceManager
Use
ResourceManager instead |
org.eclipse.rap.rwt.service.IServiceHandler
Use ServiceHandler instead.
|
org.eclipse.rap.rwt.service.IServiceManager
Use
ServiceManager instead |
org.eclipse.rap.rwt.service.IServiceStore
This interface will be removed in a future release without a replacement. If you need
to store data in the scope of a request, consider to use the request object (e.g.
HttpServletRequest#setAttribute(String, Object) ). |
org.eclipse.rap.rwt.service.ISessionStore
Use
UISession instead |
org.eclipse.rap.rwt.service.ISettingStore
Use
SettingStore instead. |
org.eclipse.rap.rwt.service.ISettingStoreFactory
Use
SettingStoreFactory instead. |
org.eclipse.rap.rwt.lifecycle.IWidgetAdapter
Use
WidgetAdapter instead. |
org.eclipse.rap.rwt.lifecycle.PhaseListener
Support for PhaseListeners is going to be removed in the future.
|
org.eclipse.rap.rwt.lifecycle.WidgetAdapter
This adapter interface was provided to facilitate the implementation of LCAs. New
custom widgets should use the RemoteObject API instead of LCAs.
|
org.eclipse.rap.rwt.lifecycle.WidgetLifeCycleAdapter
New custom widgets should use the RemoteObject API instead of LCAs.
|
Class and Description |
---|
org.eclipse.rap.rwt.lifecycle.AbstractWidgetLCA
New custom widgets should use the RemoteObject API instead of LCAs.
|
org.eclipse.rap.rwt.lifecycle.ControlLCAUtil
New custom widgets should use the RemoteObject API instead of LCAs.
|
org.eclipse.rap.rwt.widgets.ExternalBrowser
Use
UrlLauncher instead |
org.eclipse.rap.rwt.graphics.Graphics
This class will be removed in future versions. For replacements, see the
documentation of the single methods.
|
org.eclipse.rap.rwt.lifecycle.PhaseEvent
Support for PhaseListeners is going to be removed in the future.
|
org.eclipse.rap.rwt.lifecycle.PhaseId
Support for PhaseListeners is going to be removed in the future.
|
org.eclipse.rap.rwt.lifecycle.ProcessActionRunner
New applications and custom widgets should not rely on lifecycle phases anymore, as
this concept is going to be replaced. Use the
RemoteObject API instead. |
org.eclipse.rap.rwt.SessionSingletonBase
use SingletonUtil instead
|
org.eclipse.rap.rwt.lifecycle.UICallBack
This class will be removed in a future release. Use
ServerPushSession instead
to enable/disable server push. |
org.eclipse.rap.rwt.lifecycle.WidgetLCAUtil
New custom widgets should use the RemoteObject API instead of LCAs.
|
org.eclipse.rap.rwt.lifecycle.WidgetUtil
Most of the helper methods in this class will not be supported in the next release.
For the remaining methods, use org.eclipse.rap.rwt.widgets.WidgetUtil instead.
|
Field and Description |
---|
org.eclipse.rap.rwt.lifecycle.WidgetUtil.CUSTOM_VARIANT
Use
RWT.CUSTOM_VARIANT instead |
org.eclipse.rap.rwt.lifecycle.WidgetUtil.CUSTOM_WIDGET_ID
For UI tests, use the web client JavaScript API to set HTML attributes that can
be used to identify widgets. Details can be found in the Developers Guide Chapter "Scripting",
section "Widget HTML".
|
org.eclipse.rap.rwt.lifecycle.WidgetUtil.ENABLE_UI_TESTS
The system property has been moved to the internal class
RWTProperties . Please look up the name in the
documentation of WidgetUtil.CUSTOM_WIDGET_ID . |
Copyright (c) EclipseSource and others 2002, 2014.
All rights reserved. This program and the accompanying materials
are made available under the terms of the
Eclipse Public License v1.0