Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337292 - [Intro] Using the CustomizableIntroPart, after having changed the welcome page's content by registryChanged, moving to standby state causes an ArrayIndexOutOfBoundsException
Summary: [Intro] Using the CustomizableIntroPart, after having changed the welcome pag...
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7 M6   Edit
Assignee: Chris Goldthorpe CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-16 05:29 EST by Matthias Keck CLA
Modified: 2011-02-21 12:09 EST (History)
3 users (show)

See Also:


Attachments
exception stack trace (4.35 KB, text/plain)
2011-02-16 05:30 EST, Matthias Keck CLA
no flags Details
Patch (1.13 KB, patch)
2011-02-18 13:05 EST, Chris Goldthorpe CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Keck CLA 2011-02-16 05:29:13 EST
Build Identifier: 20100917-0705

When using the CustomizableIntroPart as the IIntroPart, any change to the org.eclipse.ui.intro.configExtension extension point leads to a call to org.eclipse.ui.intro.config.CustomizableIntroPart.registryChanged(IRegistryChangeEvent). After such a change the AbstractIntroPartImplementation's History object history gets cleared. An immediate change of the welcome page to standby state leads to a call of org.eclipse.ui.internal.intro.impl.model.History.getCurrentLocation() that causes an ArrayIndexOutOfBoundsException because the history vector has been cleared. 

Reproducible: Always

Steps to Reproduce:
1. Open welcome page and a Host OSGi Console.
2. Uninstall a bundle that contributes to the org.eclipse.ui.intro.configExtension extension point.
3. Double click on the welcome tab of the welcome page to send it to standby state.
Comment 1 Matthias Keck CLA 2011-02-16 05:30:49 EST
Created attachment 189080 [details]
exception stack trace
Comment 2 Chris Goldthorpe CLA 2011-02-18 12:35:16 EST
I can look into this. What are the steps to open the host OSGI console?
Comment 3 Paul Webster CLA 2011-02-18 12:37:22 EST
(In reply to comment #2)
> I can look into this. What are the steps to open the host OSGI console?

In 3.7 you can open the Console view and use the Open Console toolbar dropdown.

PW
Comment 4 Chris Goldthorpe CLA 2011-02-18 13:05:49 EST
Created attachment 189306 [details]
Patch
Comment 5 Chris Goldthorpe CLA 2011-02-18 13:06:19 EST
Patch applied to HEAD, Fixed
Comment 6 Matthias Keck CLA 2011-02-21 01:58:52 EST
Is it possible to back-integrate the patch into 3.6.x? Thanks.
Comment 7 Chris Goldthorpe CLA 2011-02-21 12:09:20 EST
3.6.2 has just been released and is the last 3.6.x point release - I could commit this fix to the 3.6 maintenance stream since it is clearly low risk but no more builds are scheduled for 3.6.