Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 393419

Summary: Remove branding API
Product: [RT] RAP Reporter: Rüdiger Herrmann <ruediger.herrmann>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: unspecified   
Target Milestone: 2.0 M3   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on:    
Bug Blocks: 374478, 377424, 393420, 393421    

Description Rüdiger Herrmann CLA 2012-11-02 09:41:26 EDT 
The branding API in RWT is obsolete. Through entry point properties all aspects can be controlled that were previously defined in a branding.

Though the branding extension point will remain in place, these changes still affect workbench code:
* the entry point/application extension should (optionally) reference a branding. For the entry point extension an ew 'branding' attribute should be created. The application extension should reference the branding through a 'branding' parameter.
* the defaultEntryPointId, servletName and associatedEntryPoints attributes are no longer needed and should be removed from the branding extension
* the name of application extension should be used as the 'path' to the entry point which represents the application
Comment 1 Rüdiger Herrmann CLA 2012-11-02 18:24:25 EDT 
Removed branding API as described. Changes are in commit d2906d206078b4bc9868471bf96c9931b8e14046.
Comment 2 Ralf Sternberg CLA 2012-11-06 03:27:04 EST 
Two minor changes:
(In reply to comment #0)
> * the entry point/application extension should (optionally) reference a
> branding. For the entry point extension an ew 'branding' attribute should be
> created. The application extension should reference the branding through a
> 'branding' parameter.

The new attribute in the entrypoint extension is now called "brandingId". Applications can specify a branding in a parameter "brandingId".

> * the name of application extension should be used as the 'path' to the entry
> point which represents the application

Instead of using the extension name, we agreed on reading the path from a "path" property of the application extension.
Comment 3 Ralf Sternberg CLA 2012-11-06 05:13:59 EST 
The exit confirmation can now be set programmatically using the client service ExitConfirmation (see bug 374478).