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

Bug 374478

Summary:	Allow adding an exit confirmation programmatically
Product:	[RT] RAP	Reporter:	Ralf Sternberg <rsternberg>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P2	CC:	ruediger.herrmann
Version:	1.5
Target Milestone:	2.0 M3
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:	393419
Bug Blocks:

Description Ralf Sternberg

2012-03-16 07:11:32 EDT

Exit confirmations can currently only be added in a branding, and brandings can only be defined in an extension. For plain applications, brandings will be replaced by entrypoint properties (bug 372257).

Since exit confirmations are not entirely static, they require a class instead of just a text, so they should not be part of the entrypoint properties but added programmatically.

Comment 1 Ralf Sternberg

2012-07-20 06:37:08 EDT

Setting to P2, we should address this in RAP 2.0.

Comment 2 Rüdiger Herrmann

2012-11-02 12:41:37 EDT

*** Bug 393420 has been marked as a duplicate of this bug. ***

Comment 3 Rüdiger Herrmann

2012-11-02 12:42:18 EDT

Once this API is there, the remaining workbench code/extension attributes that deal with exit confirmation should be removed.

Comment 4 Ralf Sternberg

2012-11-02 12:43:03 EDT

Suggestion: Provide a client service for exit confirmation feature:

public interface ExitConfirmation {
  void setMessage( String );
  String exitConfirmation.getMessage();
}

* setMessage( null ) clears the message.

Comment 5 Ralf Sternberg

2012-11-06 05:12:00 EST

Introduced ExitConfirmation as a client service in commit 0229f586dc8a4a0070913cabbbe02900b8b5e8d3.
This service is currently supported by the WebClient.