Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347883 - Create configuration API
Summary: Create configuration API
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.5 M7   Edit
Assignee: Frank Appel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-01 01:35 EDT by Frank Appel CLA
Modified: 2012-05-17 14:39 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Appel CLA 2011-06-01 01:35:58 EDT
Create an API that can be used for RWT application context initialization in arbitrary environments. With environments I mean standard webapp, OSGi bundle, integration with Spring etc.

The basic idea is to have ApplicationConfigurator interface that provides a configure( Application application ) callback method. The application instance that is passed to the callback method provides the possibility to set application specific handlers and infos (e.g. application.setServiceHandler( myHandler )).

This mechanism will replace the current configuration mechanisms in use. The ApplicationConfigurer will be registered as servlet context init parameter in web.xml or as service in an OSGi bundle.
Comment 1 Ralf Sternberg CLA 2012-05-17 14:39:42 EDT
The API described above has been contributed in RAP 1.5M1, and revised in 1.5M7. The interface is now called ApplicationConfiguration (which describes its purpose, not its functional principle). It can be registered as servlet context init parameter or as OSGi service.