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

Bug 320615

Summary: Support "Production Mode" and "Development Mode"
Product: [RT] RAP Reporter: Benjamin Wolff <eclipse>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3    
Version: 1.2   
Target Milestone: 2.0 M4   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 343068    
Bug Blocks: 321719    

Description Benjamin Wolff CLA 2010-07-22 07:26:54 EDT 
Build Identifier: 

It may be a nice feature, to add a mode where the RAP GET parameters (startup etc.) are disabled. Application start will only be possible via branding-defined URLs. The usage of this feature would make sens in very security sensitive environments (Internet) or simply to prevent exposing internal application structures.

Reproducible: Always

Steps to Reproduce:
Forum discussion: http://www.eclipse.org/forums/index.php?t=msg&th=172338&start=0&
Comment 1 Benjamin Muskalla CLA 2010-07-22 09:50:35 EDT 
I think there should be more considered in such a scenario. Not only starting applications only via branding but also disabling debug messages and enabling js compression. In my eyes, the default should be the deployment mode and for developers, we should add a switch to the launch config to enable development mode (no compression, js debug messages, startup allowed, ...)
Comment 2 Benjamin Muskalla CLA 2010-08-11 12:13:28 EDT 
Bug 320605 may be an interesting candidate for the "dev mode".
Comment 3 Ralf Sternberg CLA 2012-11-21 11:58:59 EST 
A development mode has been introduced in bug 343068. As suggested before, this mode can also affect other settings than the JavaScript compression in the future.

Since startup and theme parameters are already obsolete, there is nothing else to do here.