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

Bug 351565

Summary: The rc.rcp component remains active even if the RCP-App is not running as an AUT
Product: [Technology] Jubula Reporter: Markus Tiede <markus.tiede>
Component: RCAssignee: Zeb Ford-Reitz <zeb.ford-reitz>
Status: CLOSED FIXED QA Contact: Oliver Goetz <Oliver.Goetz>
Severity: critical    
Priority: P2 CC: alexandra.schladebeck, erdal.karaca.de
Version: 1.0.0   
Target Milestone: Indigo SR1   
Hardware: All   
OS: All   
Whiteboard:

Description Markus Tiede CLA 2011-07-08 08:49:05 EDT 
The rc.rcp component remains active - see:

http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/tree/org.eclipse.jubula.rc.rcp/src/org/eclipse/jubula/rc/rcp/accessor/Startup.java#n497

The listeners which get installed here are active even if the RCP-App is not running as an AUT. This may cause undefined performance / memory / behavior issues.
Comment 1 Zeb Ford-Reitz CLA 2011-09-09 06:41:57 EDT 
fixed with http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=2a3be8f5aa20735dce5fd8e316140d214390cefc

If the host application is not running as an AUT, the rc.rcp bundle is still activated as normal. However, the various listeners will not be registered. This means that the bundle will be "running" within the non-AUT application, but there will be no active code.
Comment 2 Markus Tiede CLA 2011-09-14 05:58:12 EDT 
Verified by code review + IDE debugging. Nice unification of rc.rcp startup. :)