| 
| Broken XML editor on Mac OS X / WPT 0.7.1 [message #146654] | Wed, 09 November 2005 05:59  |  | 
| Eclipse User  |  |  |  |  | I'm running Eclipse 3.1 on Mac OS X. I installed WPT 0.7.1 from the update site (including prereq's), primarily to check out the XML
 support. My eclipse now shows that the various features and plugins are
 installed, but if I try to open an XML file all I see is a blank page,
 and an error in the log as below.
 
 java.lang.NoClassDefFoundError:
 org/eclipse/wst/sse/ui/internal/StructuredTextEditor
 at java.lang.Class.getDeclaredConstructors0(Native Method)
 at  java.lang.Class.privateGetDeclaredConstructors(Class.java:16 18)
 at java.lang.Class.getConstructor0(Class.java:1930)
 at java.lang.Class.newInstance0(Class.java:278)
 at java.lang.Class.newInstance(Class.java:261)
 at
 org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:162)
 at
 org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:142)
 at
 org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:129)
 at
 org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 48)
 at
 org.eclipse.ui.internal.WorkbenchPlugin.createExtension(Work benchPlugin.java:232)
 at
 org.eclipse.ui.internal.registry.EditorDescriptor.createEdit or(EditorDescriptor.java:252)
 
 Either I'm missing some pre-req, or there's a bundle classpath style
 issue going on. Any clues as to how I can debug this and get my
 environment operational?
 
 (I definitely have the Web Standard Tools org.eclipse.wst 0.7.1 feature
 installed, and I see the related plugins in the list of installed
 plugins...)
 
 Thanks, Adrian.
 |  |  |  | 
| 
| Re: Broken XML editor on Mac OS X / WPT 0.7.1 [message #146667 is a reply to message #146654] | Wed, 09 November 2005 06:53   |  | 
| Eclipse User  |  |  |  |  | A partial solution to my own problem... 
 I installed 0.7.1 in an eclipse that already had 0.7.0... the install
 disables the 0.7.0 version, and enables 0.7.1. BUT, not *all* the
 plugins are updated to 0.7.1 version in the WPT 0.7.1 drop - some are
 still at 0.7.0 level and shared with WPT 0.7.0. These plugins remain
 disabled in my workspace (presumably because they are listed in the
 disabled 0.7.0, even though they are *also* listed in the enabled
 0.7.1). That seems like an eclipse platform bug to me.
 
 I've disabled 0.7.1 and re-enabled 0.7.0 and that's got me going again
 for the time being.
 
 Adrian Colyer wrote:
 > I'm running Eclipse 3.1 on Mac OS X. I installed WPT 0.7.1 from the
 > update site (including prereq's), primarily to check out the XML
 > support. My eclipse now shows that the various features and plugins are
 > installed, but if I try to open an XML file all I see is a blank page,
 > and an error in the log as below.
 >
 > java.lang.NoClassDefFoundError:
 > org/eclipse/wst/sse/ui/internal/StructuredTextEditor
 > at java.lang.Class.getDeclaredConstructors0(Native Method)
 > at  java.lang.Class.privateGetDeclaredConstructors(Class.java:16 18)
 > at java.lang.Class.getConstructor0(Class.java:1930)
 > at java.lang.Class.newInstance0(Class.java:278)
 > at java.lang.Class.newInstance(Class.java:261)
 > at
 >  org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:162)
 >
 > at
 >  org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:142)
 >
 > at
 >  org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:129)
 >
 > at
 >  org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 48)
 >
 > at
 >  org.eclipse.ui.internal.WorkbenchPlugin.createExtension(Work benchPlugin.java:232)
 >
 > at
 >  org.eclipse.ui.internal.registry.EditorDescriptor.createEdit or(EditorDescriptor.java:252)
 >
 >
 > Either I'm missing some pre-req, or there's a bundle classpath style
 > issue going on. Any clues as to how I can debug this and get my
 > environment operational?
 >
 > (I definitely have the Web Standard Tools org.eclipse.wst 0.7.1 feature
 > installed, and I see the related plugins in the list of installed
 > plugins...)
 >
 > Thanks, Adrian.
 |  |  |  | 
| 
| Re: Broken XML editor on Mac OS X / WPT 0.7.1 [message #147501 is a reply to message #146667] | Thu, 17 November 2005 11:35  |  | 
| Eclipse User  |  |  |  |  | On Wed, 09 Nov 2005 06:53:42 -0500, Adrian Colyer <adrian.colyer@gmail.c= om> wrote:
 
 > I installed 0.7.1 in an eclipse that already had 0.7.0... the install =
 disables the 0.7.0 version, and enables 0.7.1. BUT,
 > not *all* the plugins are updated to 0.7.1 version in the WPT 0.7.1 dr=
 op - some are still at 0.7.0 level and shared with
 > WPT 0.7.0. These plugins remain disabled in my workspace (presumably b=
 ecause they are listed in the disabled 0.7.0, even
 > though they are *also* listed in the enabled 0.7.1). That seems like a=
 n eclipse platform bug to me.
 >
 
 I would appreciate a bugzilla being opened on this, and this scenerio.
 It might well be we did not create our update package correctly, so, I p=
 ersonally
 don't mind where you open the bug. But ... I do want to make sure we get=
 'updates'
 working well and as expected, so we'll get someone to take a deeper look=
 ... if you
 open the bug. (I'm not sure we'll change/fix anything in 0.7.1 . but wan=
 t to be sure we
 understand the issues better as we move forward).
 |  |  |  | 
Powered by 
FUDForum. Page generated in 0.04337 seconds