Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » error on creating package explorer view
error on creating package explorer view [message #27463] Sat, 03 May 2003 18:27 Go to next message
Eclipse UserFriend
Originally posted by: jewgenij.t-online.de

Hello,
I have a problem with package explorer view after updating to eclipse 2.1.0.
I alway get the message "An error has occurred when creating this view" in
red color.
Does anybody have an idea of what I need to do ?

Thanks
Jewgenij

The .log file contains following exception:
Command-line arguments: -os win32 -ws win32 -arch x86 -install
file:C:/eclipse/

!ENTRY org.eclipse.ui.workbench 4 2 Mai 03, 2003 23:59:27.836

!MESSAGE Problems occurred when invoking code from plug-in:
"org.eclipse.ui.workbench".

!STACK 0

java.lang.NoClassDefFoundError:
org/eclipse/jdt/internal/ui/filters/AbstractFilter

at java.lang.ClassLoader.defineClass0(Native Method)

at java.lang.ClassLoader.defineClass(ClassLoader.java:509)

at java.security.SecureClassLoader.defineClass(SecureClassLoade r.java:123)

at java.net.URLClassLoader.defineClass(URLClassLoader.java:246)

at java.net.URLClassLoader.access$100(URLClassLoader.java:54)

at java.net.URLClassLoader$1.run(URLClassLoader.java:193)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:186)

at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.find Class(Delegating
URLClassLoader.java:922)

at
org.eclipse.core.internal.plugins.PluginClassLoader.internal FindClassParents
Self(PluginClassLoader.java:196)

at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.find ClassParentsSelf
(DelegatingURLClassLoader.java:485)

at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(Delegating
URLClassLoader.java:882)

at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(Delegating
URLClassLoader.java:862)

at java.lang.ClassLoader.loadClass(ClassLoader.java:262)

at
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension
(PluginDescriptor.java:130)

at
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension
(PluginDescriptor.java:167)

at
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExten
sion(ConfigurationElement.java:103)

at
org.eclipse.jdt.internal.ui.filters.FilterDescriptor.createV iewerFilter(Filt
erDescriptor.java:118)

at
org.eclipse.jdt.ui.actions.CustomFiltersActionGroup.updateBu iltInFilters(Cus
tomFiltersActionGroup.java:223)

at
org.eclipse.jdt.ui.actions.CustomFiltersActionGroup.installF ilters(CustomFil
tersActionGroup.java:186)

at
org.eclipse.jdt.ui.actions.CustomFiltersActionGroup.<init>(CustomFiltersActi
onGroup.java:101)

at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerActio nGroup. <init>(Pa
ckageExplorerActionGroup.java:118)

at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart. makeActions(Pack
ageExplorerPart.java:597)

at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart. createPartContro
l(PackageExplorerPart.java:299)

at org.eclipse.ui.internal.PartPane$4.run(PartPane.java:141)

at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java
:889)

at org.eclipse.core.runtime.Platform.run(Platform.java:413)

at org.eclipse.ui.internal.PartPane.createChildControl(PartPane .java:137)

at org.eclipse.ui.internal.ViewPane.createChildControl(ViewPane .java:211)

at org.eclipse.ui.internal.PartPane.createControl(PartPane.java :186)

at org.eclipse.ui.internal.ViewPane.createControl(ViewPane.java :190)

at
org.eclipse.ui.internal.PartTabFolder.createPartTab(PartTabF older.java:252)

at
org.eclipse.ui.internal.PartTabFolder.createControl(PartTabF older.java:224)

at
org.eclipse.ui.internal.PartSashContainer.createControl(Part SashContainer.ja
va:192)

at
org.eclipse.ui.internal.PerspectivePresentation.activate(Per spectivePresenta
tion.java:96)

at org.eclipse.ui.internal.Perspective.onActivate(Perspective.j ava:725)

at org.eclipse.ui.internal.WorkbenchPage.onActivate(WorkbenchPa ge.java:1799)

at org.eclipse.ui.internal.WorkbenchWindow$7.run(WorkbenchWindo w.java:1496)

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)

at
org.eclipse.ui.internal.WorkbenchWindow.setActivePage(Workbe nchWindow.java:1
483)

at
org.eclipse.ui.internal.WorkbenchWindow.restoreState(Workben chWindow.java:13
63)

at org.eclipse.ui.internal.Workbench.restoreState(Workbench.jav a:1263)

at org.eclipse.ui.internal.Workbench.access$10(Workbench.java:1 223)

at org.eclipse.ui.internal.Workbench$12.run(Workbench.java:1141 )

at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java
:889)

at org.eclipse.core.runtime.Platform.run(Platform.java:413)

at
org.eclipse.ui.internal.Workbench.openPreviousWorkbenchState (Workbench.java:
1093)

at org.eclipse.ui.internal.Workbench.init(Workbench.java:870)

at org.eclipse.ui.internal.Workbench.run(Workbench.java:1373)

at
org.eclipse.core.internal.boot.InternalBootLoader.run(Intern alBootLoader.jav
a:845)

at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39
)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl
..java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at org.eclipse.core.launcher.Main.basicRun(Main.java:249)

at org.eclipse.core.launcher.Main.run(Main.java:707)

at org.eclipse.core.launcher.Main.main(Main.java:543)
Re: error on creating package explorer view [message #27512 is a reply to message #27463] Mon, 05 May 2003 04:00 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: daniel.megert.gmx.net

JT wrote:

>Hello,
>I have a problem with package explorer view after updating to eclipse 2.1.0.
>I alway get the message "An error has occurred when creating this view" in
>red color.
>Does anybody have an idea of what I need to do ?
>
This looks like a compatibility problem when using an existing workspace
to 2.1. Please file a bug report for this.
For now you have 2 choices
1. Start with a fresh workspace (recommended because you get all new
settings and don't carry on old/deprecated settings).
2. First close all PackageExplorers in all perspectives and exit. In
..metadata/.plugins/org.eclipse.jdt.ui/pref_store.ini delete all
key=value pairs of which the key starts with "CustomFiltersActionGroup".
This will reset all the filters. You should now be able to start and
open the PackageExplorer again.

HTH
Dani
Re: error on creating package explorer view [message #27559 is a reply to message #27512] Mon, 05 May 2003 10:33 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: daniel.megert.gmx.net

Daniel Megert wrote:

> JT wrote:
>
>> Hello,
>> I have a problem with package explorer view after updating to eclipse
>> 2.1.0.
>> I alway get the message "An error has occurred when creating this
>> view" in
>> red color.
>> Does anybody have an idea of what I need to do ?
>>
> This looks like a compatibility problem when using an existing
> workspace to 2.1. Please file a bug report for this.

I filed bug 37215: createExecutableExtension does not catch missing
super class
http://bugs.eclipse.org/bugs/show_bug.cgi?id=37215

Dani
Re: error on creating package explorer view [message #27598 is a reply to message #27512] Mon, 05 May 2003 14:38 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: kc.sfschools.org

I'm unable to open the package explorer view, but my stack
trace is slightly different. I included it below.

In my case there are no CustomFiltersActionGroup preferences
in pref_store.ini. I tried scrubbing pref_store.ini clean,
but that did not help. The crash first appeared this
morning. I had been using 2.1 and the package explorer for
a few weeks without incident. The other puzzle is that the
supposedly missing class,
CustomFiltersActionGroup$ShowFilterDialogAction, is present
in the 2.1 jdt.jar but not in the 2.0 version. Is there
some way that my 2.0 plugins are visible to the
cloassloader?

> This looks like a compatibility problem when using an existing workspace
> to 2.1. Please file a bug report for this.

Is there any good summary info on these incompatibilities
and on upgrade considerations?

I installed 2.1 in parallel with 2.0 since I wanted to do
some testing to ensure it would work Ok on my projects with
our plugins. 2.0 was in c:\eclipse and 2.1 was in
c:\eclipse2.1. I was surprised and alarmed when 2.1
silently found all my projects in c:\eclipse\workspace and
started working on them. I wanted to and expected to have
to manually import old projects as you recommend.

I was more alarmed when I found out that I could no longer
run 2.0! WTF??? I was trying to act cautiously, but
Eclipse was too smart for that and just plunged me head
first into 2.1 -- no going back.

Now I'm learning that there are compatibility and upgrade
issues between 2.0 and 2.1? Please tell me more.

Cheer,
KC Jones

I'm running 2.1 on Win2K. .metadata/.log looks like:

!SESSION May 05, 2003 11:14:42.607 ---------------------------------------------
java.version=1.4.0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -install file:C:/eclipse2.1/
!ENTRY org.eclipse.ui.workbench 4 2 May 05, 2003 11:14:42.617
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
!STACK 0
java.lang.NoClassDefFoundError: org/eclipse/jdt/ui/actions/CustomFiltersActionGroup$ShowFilt erDialogAction
at org.eclipse.jdt.ui.actions.CustomFiltersActionGroup.fillView Menu(CustomFiltersActionGroup.java:153)
at org.eclipse.jdt.ui.actions.CustomFiltersActionGroup.fillActi onBars(CustomFiltersActionGroup.java:109)
at org.eclipse.jdt.internal.ui.actions.CompositeActionGroup.fil lActionBars(CompositeActionGroup.java:68)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActio nGroup.fillActionBars(PackageExplorerActionGroup.java:206)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart. fillActionBars(PackageExplorerPart.java:495)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart. createPartControl(PackageExplorerPart.java:338)
at org.eclipse.ui.internal.PartPane$4.run(PartPane.java:141)
at org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:889)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at org.eclipse.ui.internal.PartPane.createChildControl(PartPane .java:137)
at org.eclipse.ui.internal.ViewPane.createChildControl(ViewPane .java:211)
at org.eclipse.ui.internal.PartPane.createControl(PartPane.java :186)
at org.eclipse.ui.internal.ViewPane.createControl(ViewPane.java :190)
at org.eclipse.ui.internal.PartTabFolder.createPartTab(PartTabF older.java:252)
at org.eclipse.ui.internal.PartTabFolder.replaceChild(PartTabFo lder.java:684)
at org.eclipse.ui.internal.PartTabFolder.replace(PartTabFolder. java:624)
at org.eclipse.ui.internal.PerspectivePresentation.addPart(Pers pectivePresentation.java:189)
at org.eclipse.ui.internal.Perspective.showView(Perspective.jav a:1481)
at org.eclipse.ui.internal.WorkbenchPage.busyShowView(Workbench Page.java:655)
at org.eclipse.ui.internal.WorkbenchPage.access$9(WorkbenchPage .java:634)
at org.eclipse.ui.internal.WorkbenchPage$13.run(WorkbenchPage.j ava:2777)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage .java:2774)
at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage .java:2764)
at org.eclipse.ui.internal.ShowViewAction.run(ShowViewAction.ja va:46)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:842 )
at org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:456)
at org.eclipse.jface.action.ActionContributionItem.handleWidget Event(ActionContributionItem.java:403)
at org.eclipse.jface.action.ActionContributionItem.access$0(Act ionContributionItem.java:397)
at org.eclipse.jface.action.ActionContributionItem$ActionListen er.handleEvent(ActionContributionItem.java:72)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:1838)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :1545)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at org.eclipse.core.internal.boot.InternalBootLoader.run(Intern alBootLoader.java:845)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
at org.eclipse.core.launcher.Main.run(Main.java:747)
at org.eclipse.core.launcher.Main.main(Main.java:583)
Re: error on creating package explorer view [message #27666 is a reply to message #27598] Tue, 06 May 2003 03:54 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: daniel.megert.gmx.net

KC Jones wrote:

>I'm unable to open the package explorer view, but my stack
>trace is slightly different. I included it below.
>
>In my case there are no CustomFiltersActionGroup preferences
>in pref_store.ini. I tried scrubbing pref_store.ini clean,
>but that did not help. The crash first appeared this
>morning. I had been using 2.1 and the package explorer for
>a few weeks without incident. The other puzzle is that the
>supposedly missing class,
>CustomFiltersActionGroup$ShowFilterDialogAction, is present
>in the 2.1 jdt.jar but not in the 2.0 version. Is there
>some way that my 2.0 plugins are visible to the
>cloassloader?
>
>
>
>>This looks like a compatibility problem when using an existing workspace
>>to 2.1. Please file a bug report for this.
>>
>>
>
>Is there any good summary info on these incompatibilities
>and on upgrade considerations?
>
The readme ;-)?

>I installed 2.1 in parallel with 2.0 since I wanted to do
>some testing to ensure it would work Ok on my projects with
>our plugins. 2.0 was in c:\eclipse and 2.1 was in
>c:\eclipse2.1. I was surprised and alarmed when 2.1
>silently found all my projects in c:\eclipse\workspace and
>started working on them.
>
Not sure what you mean here. Per default Eclipse puts/uses the workspace
embedded in its install directory and calls it workspace. In your case
this would be
c:\eclipse\workspace
c:\eclipse2.1\workspace
There are no smarts to link them together. Except if
- you start both eclipse installs with -data X where X is the same
- you copied one workspace from one location to the other (i.e. you
might have copied absolute path)

> I wanted to and expected to have
>to manually import old projects as you recommend.
>
That's ok.

>I was more alarmed when I found out that I could no longer
>run 2.0! WTF???
>
Did you touch the 2.0 workspace with 2.1 install and then again with
2.0? This is not supported.

> I was trying to act cautiously, but
>Eclipse was too smart for that and just plunged me head
>first into 2.1 -- no going back.
>
Eclipse is smart in the sense that you should be able to start a 2.0
workspace with a 2.1 installation. After that you have to consider this
workspace a 2.1 workspace and starting 2.1 workspaces with 2.0 is not
supported (read the workspace compatibility section in the readme).

>Now I'm learning that there are compatibility and upgrade
>issues between 2.0 and 2.1? Please tell me more.
>
Again, read the readme. The problem described by the JT is not covered
there. That's why I filed a bug report.

HTH
Dani
Re: error on creating package explorer view [message #28403 is a reply to message #27666] Tue, 06 May 2003 14:25 Go to previous message
Eclipse UserFriend
Originally posted by: kc.sfschools.org

> >Is there any good summary info on these incompatibilities
> >and on upgrade considerations?
> >
> The readme ;-)?

That's pretty glib. Also not helpful.

Turns out my crash was a classpath issue. I also tend to
think it is a bug, but its debatable I suppose.

What happened was I installed 2.1 in parallel with 2.0, as
noted earlier. But I launched 2.1 using a 2.0 desktop
shortcut that I modified to point to the 2.1 eclipse.exe.

The shortcut specified the 2.0 directory as the working
directory. By starting 2.1 (c:\eclipse2.1\eclipse.exe) in
the 2.0 directory (c:\eclipse), 2.1 silently "found" and
upgraded all my 2.0 workspaces. Note that the shortcut does
not set any command line arguments, so there was no -data
option specified.

The confused 2.1 also appears to have found both the 2.0 and
2.1 plugins and was confused about which to use, hence the
NoClassDefFoundError crash.

The readme does not discuss where to launch eclipse.exe, nor
any impact of setting the working directory.

I'm still confused as to why 2.1 was working OK for a few
weeks before developing this Package Explorer ailment.
Presumably there was some workspace state that arose from my
edits that triggered a 2.1 feature?

In a perfect world I would expect eclipse.exe to validate
its working directory if it in fact uses that directory for
some reason. It could read the install.ini or
eclipseproduct files found there and kvetch when it finds
itself running in a older version's working directory.

I'll file the bug report if anyone else agrees that there is
a bug here. Otherwise I'm back to work...

Cheers,
KC
Previous Topic:Problems with shortcuts in windows98
Next Topic:Base Non-IDE Application Using the Workbench
Goto Forum:
  


Current Time: Sat Jul 19 17:50:00 EDT 2025

Powered by FUDForum. Page generated in 0.05515 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top