- This topic has 39 replies, 9 voices, and was last updated 20 years, 3 months ago by
.
-
Posts
-
An interesting thing:
When I flick back to the Design view and it’s blank, I press F5 to refresh. The word “null” is written to the designer edit area and then comes a dialog box:
“HTML source contains syntax errors that prevent the design mode from being activated. Please correct these errors and try again……”
Phil
!ENTRY org.eclipse.osgi Aug 16, 2004 23:47:44.656
!MESSAGE The class “com.ibm.wtp.common.ui.UITesterImpl” cannot be loaded because the system is shutting down and the plug-in “com.ibm.wtp.common.ui” has already been stopped.
!STACK 0
java.lang.ClassNotFoundException: The class “com.ibm.wtp.common.ui.UITesterImpl” cannot be loaded because the system is shutting down and the plug-in “com.ibm.wtp.common.ui” has already been stopped.
at org.eclipse.core.runtime.adaptor.EclipseClassLoader.shouldActivateFor(EclipseClassLoader.java:147)
at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:62)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:371)
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:402)
at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:93)
at java.lang.ClassLoader.loadClass(Unknown Source)
at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:307)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:336)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1313)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:131)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:124)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:113)
at com.ibm.wtp.common.UIContextDetermination$UITesterRegistryReader.readElement(UIContextDetermination.java:153)
at com.ibm.wtp.common.RegistryReader.internalReadElement(RegistryReader.java:61)
at com.ibm.wtp.common.RegistryReader.readRegistry(RegistryReader.java:99)
at com.ibm.wtp.common.UIContextDetermination.getCurrentContext(UIContextDetermination.java:69)
at com.ibm.etools.validate.internal.EventManager.isHeadless(EventManager.java:431)
at com.ibm.etools.validate.internal.EventManager.shutdown(EventManager.java:323)
at com.ibm.etools.validate.plugin.ValidationPlugin.shutdown(ValidationPlugin.java:137)
at org.eclipse.core.internal.compatibility.PluginActivator.stop(PluginActivator.java:74)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:994)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:990)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:502)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.stop(AbstractBundle.java:437)
at org.eclipse.core.runtime.adaptor.BundleStopper.basicStopBundles(BundleStopper.java:75)
at org.eclipse.core.runtime.adaptor.BundleStopper.stopBundles(BundleStopper.java:62)
at org.eclipse.core.runtime.adaptor.EclipseAdaptor.frameworkStopping(EclipseAdaptor.java:551)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:457)
at org.eclipse.osgi.framework.internal.core.SystemBundle$1.run(SystemBundle.java:182)
at java.lang.Thread.run(Unknown Source)!ENTRY org.eclipse.core.runtime 4 1 Aug 16, 2004 23:47:44.671
!MESSAGE Plug-in com.ibm.wtp.common.ui was unable to load class com.ibm.wtp.common.ui.UITesterImpl.
!STACK 0
java.lang.ClassNotFoundException: com.ibm.wtp.common.ui.UITesterImpl
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:404)
at org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:93)
at java.lang.ClassLoader.loadClass(Unknown Source)
at org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:307)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:336)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1313)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:131)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:124)
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:113)
at com.ibm.wtp.common.UIContextDetermination$UITesterRegistryReader.readElement(UIContextDetermination.java:153)
at com.ibm.wtp.common.RegistryReader.internalReadElement(RegistryReader.java:61)
at com.ibm.wtp.common.RegistryReader.readRegistry(RegistryReader.java:99)
at com.ibm.wtp.common.UIContextDetermination.getCurrentContext(UIContextDetermination.java:69)
at com.ibm.etools.validate.internal.EventManager.isHeadless(EventManager.java:431)
at com.ibm.etools.validate.internal.EventManager.shutdown(EventManager.java:323)
at com.ibm.etools.validate.plugin.ValidationPlugin.shutdown(ValidationPlugin.java:137)
at org.eclipse.core.internal.compatibility.PluginActivator.stop(PluginActivator.java:74)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:994)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:990)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:502)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.stop(AbstractBundle.java:437)
at org.eclipse.core.runtime.adaptor.BundleStopper.basicStopBundles(BundleStopper.java:75)
at org.eclipse.core.runtime.adaptor.BundleStopper.stopBundles(BundleStopper.java:62)
at org.eclipse.core.runtime.adaptor.EclipseAdaptor.frameworkStopping(EclipseAdaptor.java:551)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:457)
at org.eclipse.osgi.framework.internal.core.SystemBundle$1.run(SystemBundle.java:182)
at java.lang.Thread.run(Unknown Source)Phillip,
The stack trace is unrelated. It’s simply caused by the runtime attempting to start up a plugin during workspace shutdown. It’s completely harmless.
Just to rule out something common in all your HTML files, can you send us one that exhibits this behavior to support@genuitec.com?
Hi Scott. I don’t need to send one. Here it is:
<!DOCTYPE html PUBLIC “-//W3C//DTD HTML 3.2//EN”>
<html>
<head>
<title></title>
</head><body>
Hello World!
</body>
</html>Phil
Phil,
Well, at least we know it’s not the HTML. Naturally, that works fine on my install. Any word on if 3.8 Beta 2 worked with Windows XP SP2?
Hvae you guys got a test machine with Windows SP2 on?
I rolled back to Eclipse 3 original and MyEclipse beta 2 where this used to work, but same problem. Only thing that changed for me lately was installing Office 2003 and XP SP2.
So:
It’s *not* 3.8.0 GA.
Gotta be XP SP2…
Phil
Phil,
Actually, we haven’t installed SP2 because we saw this post:
http://support.microsoft.com/default.aspx?kbid=884130&product=windowsxpsp2that lists Eclipse 3 as an application that “might behave differently” with SP2 installed. We thought we’d let others find out “how” different. Thanks for closing the loop and letting us know that there is definately an issue when SP2 is installed. I’m sure we’ll load up a test machine to look at it for the next maintenance release. We really appreciate your help in isolating the issue for us.
OK, Scott. But I think you ought to test with SP2 pretty soon as there’s going to be a lot of people installing it…
Phil
I’m using Eclipse Version: 3.0.0 Build id: 200406251208 with
myEclipse 3.8-B2 on a test machine with XP-SP2.
(We are still evaluating SP2.)The HTML designer seems to be working fine for my system.
I don’t think I have office 2000, the MS dialog did not appear when first opening the HTML designer.Hope this helps,
DamonI’m not aware of any explicit testing we did for 3.8.1 and SP2, we had a laundry list of “must stabalize” items that were not necessarily related to SP2 compat problems.
I am fairly certain we will look into this seriously for 3.8.2 as SP2 rollout is going to start heating up here as MS releases it on Windows Update.
Phil,
We tested on SP2 without MS Office installed and the visual designer worked correctly. So, it appears to be something that the Office / SP2 combination has that is causing problems. However, do you really think you need to “leave off” ME just because one small portion is problematic? Is the visual designer the only part of the product you use? If you’re looking for a workaround, since you have MS Office installed you likely have MS Frontpage as part of it. You could certainly use that to visually edit your HTML pages within your Eclipse project and then use MyEclipse to deploy your application, etc, couldn’t you?
