Skip to main content
AgeCommit message (Collapse)AuthorFilesLines
2014-01-21Update RAP Runtime to RAP 2.1.2Markus Knauer2-15/+15
- Update version numbers in pom.xml, MANIFEST.MF, feature.xml - Update dependencies in feature.xml and category.xml - Adjust copyright headers where appropriate
2013-09-02Update RAP Runtime bundle versions and package exports to 2.1.1Markus Knauer2-13/+13
2013-08-13Get workbench instance from IWorkbenchLocationServiceIvan Furnadjiev1-2/+2
343082: IllegalStateException from WorkbenchMenuService when extension registry changed
2013-07-02Update features and build artifacts from 2.1.0 to 2.1.1 for Kepler SR1Markus Knauer1-1/+1
2013-05-06Update RAP package exports/imports and dependencies to version 2.1.0Markus Knauer1-15/+15
2013-02-25Replace try-catch in SessionLocaleProviderRalf Sternberg1-3/+5
The extension registry is also accessed outside of a UISession, e.g. when reading global contributions at application startup. This is not an exceptional case and should not be handled by an exception. An odd side effect is that all these exceptions, although catched, end up in the profiler logs.
2013-02-22Backport the fix from bug 226155Ivan Furnadjiev1-1/+4
325788: FilteredTree assumes parent uses GridLayout, ends in a ClassCastException
2013-02-20Upgrade RAP Runtime versions from 2.0 to 2.1Markus Knauer2-4/+4
Adjust versions in pom.xml, feature.xml, MANIFEST.MF, category.xml, .product, and other files. This does not yet include export package declarations in MANIFEST.MF.
2013-01-07Replace the usage of deprecated Graphics#textExtent withIvan Furnadjiev1-36/+37
2013-01-01Eliminate RWTFactoryRalf Sternberg1-3/+4
RWTFactory is a facade that provides access to application-scoped instances. It's a bunch of getters that simply delegate to the application context. For internal use, this facade is not really needed. Obtaining instances directly from the ApplicationContextImpl results in slightly more verbose code, but it makes the structure more obvious. Move static method getApplicationContext() to ContextProvider, which already provides access to the service context and UISession. Use static import for ContextProvider.getApplicationContext(). I think we should generally use static imports for ContextProvider#getXxx. This makes the code more readable and compensates for the added verbosity. As an example, instead of RWTFactory.getEntryPointManager() we have now getApplicationContext().getEntryPointManager()
2012-12-30Fix copyright headers of files modified in 2012Ralf Sternberg6-32/+38
2012-12-19Use objects instead of strings to activate server pushRalf Sternberg1-4/+2
ServerPushManager accepts objects as handles now. So we can use objects directly instead of creating Strings.
2012-12-14Replace SettingStoreException with IOExceptionRalf Sternberg5-21/+33
It seems that the only good reason for a checked exception in a setting store operation is an I/O problem. Any other problem should result in an unchecked exception. There is no need for a specialized exception type only for setting store implementations.
2012-12-14Remove prefix "RWT" from FileSettingStoreFactoryRalf Sternberg1-1/+1
2012-12-14Remove I-prefix from public setting store interfacesRalf Sternberg6-49/+52
ISettingStore -> SettingStore ISettingStoreFactory -> SettingStoreFactory * Leave old interfaces in place to leave a pointer for the migration * Revise setting store API documentation See bug 391724: Remove "I" prefix from interfaces
2012-12-13Rename internal uicallback package to serverpushRalf Sternberg1-1/+1
2012-12-13Rename internal UICallBack classes to ServerPushRalf Sternberg1-3/+3
Server push is the established term for technologies that "push" updates from server to client. We should adopt this naming and get rid of the misleading name "uicallback" in the framework.
2012-12-13Replace UICallBack#runNonUIThreadWithFakeContext with RWT#getUISession(Ivan Furnadjiev8-71/+69
display)#exec( ... )
2012-12-12Rename IApplicationStore to ApplicationContextRalf Sternberg1-2/+2
The new name "ApplicationContext" is not limited to storing values, it can later also be used to obtain application-wide instances of framework services, such as the ThemeManager or the ResourceManager. Moreover, the ApplicationContext is related to the ServletContext, which fits well with the new name. HttpSession <---> UISession ServletContext <---> ApplicationContext Suffix the existing internal class ApplicationContext with "Impl" and let it implement ApplicationContext. Revise API documentation, leave compatibility API for IApplicationStore in place.
2012-12-12Remove HttpSessionBindingListener support in UISessionRalf Sternberg4-152/+145
For historical reasons, UISession supported attributes that implement HttpSessionBindingListener. Whenever an attribute was set, removed, or overwritten, and the attribute value implemented this interface, the listener methods valueBound/Unbound have been called by the UISession. This feature does not fit in with the distinction between UISession and HttpSession. Apparently, it had been implemented for internal use in the workbench. These cases are replaced by UISessionListener.
2012-12-10Rename session store to UISessionRalf Sternberg14-112/+123
To make the difference between the HttpSession and RAP's UI session more obvious, we decided to rename the ISessionStore to UISession. * SessionStore -> UISession * SessionStoreListener -> UISessionListener * SessionStoreEvent -> UISessionEvent Also rename internal classes and variables. RWT has a new method getUISession(). To provide a clue for developers migrating to RAP 2.0, the interface ISessionStore remains in place as deprecated type. For SessionStoreListener and SessionStoreEvent, there is no such compatibility version.
2012-12-08Move ResourceManager and ResourceLoader to service packageRalf Sternberg4-4/+4
It seems to make sense to group services provided by the framework in one package named "service". ResourceManager is such a service, quite similar to ServiceManager. Also organize imports in rwt and rwt.test.
2012-12-08Use entrypoint extensions also for IApplicationRalf Sternberg1-60/+45
Since application extensions (IApplication) can not be referenced from a branding extension anymore, we supported a "path" and a "brandingId" parameter for application extensions instead in RAP 2.0M3. This turned out to create 2 problems: 1) Third-party bundles may contain application extensions that lead to an exception in RAP because they don't have a path parameter. 2) Application extensions in third-party bundles have to be modified in order to be made available in RAP. Fix this with an alternative approach: Application extensions can be made available in RAP by a separate entrypoint extension using a new parameter "applicationId". Path and branding can be specified in the same way as for "normal" entrypoints. Also add an example extension to the workbench demo to be able to test this feature. See bug 394805: "The parameter 'path' must not be null" when running RAP with Workbench
2012-12-08Remove dead branding codeRalf Sternberg4-88/+0
2012-12-07Adjust all project pom.xml files to new parent pom location.Markus Knauer1-1/+1
2012-12-05Workbench: concat and register JS resources from extensionsRalf Sternberg3-141/+236
JavaScript resources registered with the resources extension point are now concatenated and registered by the workbench application config. Code for reading and registering of resources moved to separate classes. Add some unused resources to be able to test resource extensions manually. See bug 393397: Provide API to load Javascript resources
2012-12-03Rename and move IEntryPoint and IEPFactoryRalf Sternberg2-9/+9
* Remove "I"-prefix from interfaces See bug 391724: Remove "I" prefix from interfaces * Move EntryPoint and EPFactory to application package EntryPoint is the central interface needed to define an application, it has nothing to do with the RWT lifecycle. * Add compatibility interfaces IEP and IEPF to ease migration * Revise documentation for EntryPoint and factory
2012-12-01Rename IResourceManager to ResourceManagerRalf Sternberg1-1/+1
See bug 391724: Remove "I" prefix from interfaces
2012-11-30Rename IServiceHandler to ServiceHandlerRalf Sternberg1-2/+2
See bug 391724: Remove "I" prefix from interfaces
2012-11-21Update namespace in FileSettingStore system propertyRalf Sternberg1-10/+10
393850: Replace obsolete namespace org.eclipse.rwt in system properties
2012-11-06Refactoring: inline method in EntryPointManagerRalf Sternberg1-1/+7
2012-11-06Merge methods from EntryPointUtil into EntryPointManagerRüdiger Herrmann2-4/+4
2012-11-05Rename branding to brandingId in entry pointRüdiger Herrmann1-19/+24
2012-11-05Qualified runtime branding attribute nameRüdiger Herrmann1-1/+1
2012-11-04Remove ApplicationImpl#addEntryPointByParameter() and related codeRüdiger Herrmann1-0/+1
Bug 393421: Remove code to add entry points by parameter
2012-11-03Remove functionless methods from IResourceRalf Sternberg2-125/+16
As of commit 14bd2c71ee2d8e34b13e1a2c8cc55cbee29070da, the IResource methods getRegisterOptions and getCharset do not have an effect anymore. They would be misleading if not removed.
2012-11-03Increase workbench bundle version to 2.0Ralf Sternberg2-13/+13
* Breaking API change in resources extension point due to move of IResource interface from RWT to workbench * Planned changes to branding extension point (see bug 377424)
2012-11-02Remove branding API from RWTRüdiger Herrmann15-238/+565
All remaining code necessary to support the branding extension was moved to internal packages in ui.workbench. Bug 393419: Remove branding API
2012-11-02Register application entry points by pathRüdiger Herrmann2-8/+7
The 'name' attribute of the 'applications' extension will be used as the path Bug 393419: Remove branding API
2012-11-02Changed reference to moved IResource interface in resources extension pointRüdiger Herrmann1-1/+1
2012-10-31Move IResource and RegisterOptions to org.eclipse.rap.ui.workbenchRüdiger Herrmann4-9/+212
The two classes are only used by the workbench and thus are moved there. They are now in package org.eclipse.rap.ui.resources. Bug 393077: Simplify ResourceManager API
2012-10-31Update all .project files to set version qualifier baseline.Markus Knauer1-1/+1
The build version qualifier is derived from the last change in a project. This dummy commit changes all .project files and adds a whitespace to the comment-element to ensure that all qualifiers start with todays date. Change build qualifier generation in RAP Runtime and Tools build
2012-10-30Remove unnecessary synchronize block in JSLibraryConcatenatorRüdiger Herrmann1-2/+1
2012-10-12Merge branch 'features/event-system-rewrite'Ruediger Herrmann2-32/+12
2012-10-09Ongoing work on 334028: Rework event systemRüdiger Herrmann2-32/+12
2012-10-09Make NLS methods genericIvan Furnadjiev9-34/+16
391431: Make NLS generic
2012-09-24Remove outdated p2.inf files from bundles.Markus Knauer1-5/+0
2012-09-22Remove support for adapter factoriesRalf Sternberg1-29/+0
- Remove the API class AdapterFactory - Remove the extension point org.eclipse.rap.ui.adapterfactory The use of adapters in RWT is an internal detail and should not be exposed as API. Moreover, the extensibility of the adapter framework (adapter manager and pluggable adapter factories ) is not needed by RWT itself. Adapter factories had been deprecated as of 1.5. See bug 344541: Deprecate AdapterFactory
2012-09-19Consolidate negated p2 requirements to org.eclipse.rap.featureMarkus Knauer1-5/+4
Having the negated p2 requirements in all bundles causes downstream builds to fail with unsatisfiable dependencies. This may be an error in the build technology (Tycho and/or p2), but by moving the negated p2 requirements to the RAP feature this issue should be solved. If it works further clean-up is required.
2012-09-19Change negated p2 requirements from IU to osgi.bundleMarkus Knauer1-1/+1
Instead of requiring a p2 IU not to be there, this change ensures that there is no OSGi bundle with the specific IDs installed.

Back to the top