| IWAV0125E "DebugGraphics.NONE_OPTION" is too complicated [message #90041] |
Sun, 08 May 2005 00:55  |
Eclipse User |
|
|
|
Originally posted by: no.ddress.here
Installed VE with the correct dependencies for 3.1M6. When I use the
Visual Class wizard, I get a frame which looks correct.
However, if I click on the content pane, the properties view shows a
"debugGraphicsOptions" property with the value "IWAV0104E ERROR - Value
not one of the enumerated values"
Visual composition does not work: dropping a button on the content pane
looks correct and a getJButton() method is created, but VE does not
generate the expected linking code (jContentPane.add(getJButton() ... ))
in getContentPane() method.
Cleaning the workspace does not help. Switching to a completely new and
empty workspace *does* enable VE to work as expected. I have too much
good stuff in my current workspace to manually transfer the projects.
Any clues as to the problem and a (practical) way to fix up my existing
workspace?
Thanks
!SESSION 2005-05-07 21:24:33.157
-----------------------------------------------
eclipse.buildId=I20050401-1645
java.version=1.5.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 -clean -data D:
\DevFiles\EclipseWorkSpace31M6
!ENTRY org.eclipse.jem.proxy 2 0 2005-05-07 21:24:33.157
!MESSAGE java.lang.RuntimeException
at org.eclipse.jem.internal.proxy.initParser.Static.evaluate
(Static.java:123)
at
org.eclipse.jem.internal.proxy.initParser.InitializationStri ngParser.eva
luate(InitializationStringParser.java:157)
at org.eclipse.jem.internal.proxy.vm.remote.ConnectionHandler.r un
(ConnectionHandler.java:236)
at org.eclipse.jem.internal.proxy.vm.remote.ConnectionThread.ru n
(ConnectionThread.java:47)
!ENTRY org.eclipse.ve.java.core 2 0 2005-05-07 21:24:33.167
!MESSAGE
+++ Warning +++: Sat May 07 21:24:33 PDT 2005 Unable to create
enumeration value for DebugGraphics.NONE_OPTION
!ENTRY org.eclipse.ve.java.core 2 0 2005-05-07 21:24:33.167
!MESSAGE Exception thrown.
!STACK 0
java.lang.InstantiationException: IWAV0125E "DebugGraphics.NONE_OPTION"
is too complicated to be evaluated
at
org.eclipse.jem.internal.proxy.remote.REMStandardBeanProxyFa ctory.create
BeanProxy(REMStandardBeanProxyFactory.java:262)
at
org.eclipse.jem.internal.proxy.remote.REMAbstractBeanTypePro xy.newInstan
ce(REMAbstractBeanTypeProxy.java:536)
at
org.eclipse.jem.internal.proxy.remote.REMIntegerTypeBeanType Proxy.newIns
tance(REMIntegerTypeBeanTypeProxy.java:103)
at
org.eclipse.ve.internal.java.core.EnumeratedLabelProvider.ge tEnumeratedV
alues(EnumeratedLabelProvider.java:51)
at
org.eclipse.ve.internal.java.core.EnumeratedLabelProvider.ge tText
(EnumeratedLabelProvider.java:90)
at
org.eclipse.ve.internal.propertysheet.AbstractPropertySheetE ntry.getValu
eAsString(AbstractPropertySheetEntry.java:722)
at org.eclipse.ui.views.properties.PropertySheetViewer.updateEn try
(PropertySheetViewer.java:1220)
at org.eclipse.ui.views.properties.PropertySheetViewer.createIt em
(PropertySheetViewer.java:359)
at
org.eclipse.ui.views.properties.PropertySheetViewer.updateCh ildrenOf
(PropertySheetViewer.java:1177)
at org.eclipse.ui.views.properties.PropertySheetViewer.access$2
(PropertySheetViewer.java:1101)
at org.eclipse.ui.views.properties.PropertySheetViewer
$3.childEntriesChanged(PropertySheetViewer.java:308)
at
org.eclipse.ve.internal.propertysheet.AbstractPropertySheetE ntry.fireChi
ldEntriesChanged(AbstractPropertySheetEntry.java:373)
at
org.eclipse.ve.internal.propertysheet.AbstractPropertySheetE ntry.refresh
ChildEntries(AbstractPropertySheetEntry.java:831)
at
org.eclipse.ve.internal.propertysheet.AbstractPropertySheetE ntry.setValu
es(AbstractPropertySheetEntry.java:1013)
at org.eclipse.ui.views.properties.PropertySheetViewer.setInput
(PropertySheetViewer.java:875)
at
org.eclipse.ui.views.properties.PropertySheetPage.selectionC hanged
(PropertySheetPage.java:392)
at
org.eclipse.ve.internal.propertysheet.EToolsPropertySheetPag e.superSelec
tionChanged(EToolsPropertySheetPage.java:230)
at
org.eclipse.ve.internal.propertysheet.EToolsPropertySheetPag e.access$2
(EToolsPropertySheetPage.java:223)
at org.eclipse.ve.internal.propertysheet.EToolsPropertySheetPag e
$1.run(EToolsPropertySheetPage.java:216)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages
(Synchronizer.java:118)
at org.eclipse.swt.widgets.Display.runAsyncMessages
(Display.java:2871)
at org.eclipse.swt.widgets.Display.readAndDispatch
(Display.java:2530)
at org.eclipse.ui.internal.Workbench.runEventLoop
(Workbench.java:1570)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1534)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench
(Workbench.java:306)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench
(PlatformUI.java:143)
at org.eclipse.ui.internal.ide.IDEApplication.run
(IDEApplication.java:103)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run
(PlatformActivator.java:228)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:315 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:268)
at org.eclipse.core.launcher.Main.run(Main.java:942)
at org.eclipse.core.launcher.Main.main(Main.java:926)
|
|
|
|
|
| Re: IWAV0125E "DebugGraphics.NONE_OPTION" is too complicated [message #90118 is a reply to message #90104] |
Sun, 08 May 2005 15:22  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Actually I'm glad you came up with this problem! A few weeks ago I was
tearing my hair out working with another person getting a similar error.
But I couldn't track it down. In her case it was a property that we had
supplied an enumeration for and I couldn't see how our BeanInfo could
come up bad like that.
Your case was the key to finding the problem because for you it was
debugGraphicsOption. We don't even provide an enumeration for that
property! So that clued me in to there being another BeanInfo and I was
able to track it down to dt.jar then. Thanks!
Gerald Rosenberg wrote:
> In article <d5lfll$pf0$1@news.eclipse.org>, richkulp@us.NO_SPAM.ibm.com
> says...
>
>>Found part of your problem. You have dt.jar in your classpath somewhere.
>>This is Sun's version of the Swing beaninfo, and it conflicts with ours,
>> but there is no way to override theirs. You don't need it, it has
>>nothing but beaninfo stuff in it.
>>
>>That cause the problem with the debugGraphicsOption. After you remove
>>the jar you will need to do a clean all projects build because we need
>>to clear out some cached info.
>
>
> Great catch! Did have the dt.jar in for the legacy reason that it
> contains the SwingBeanInfo.class (but, it has been dropped as of Java 5,
> so I had pulled the class out anyway - just did not think to remove the
> jar).
>
> Everything is now working as expected.
>
> Thanks again.
--
Thanks,
Rich Kulp
|
|
|
| Re: IWAV0125E "DebugGraphics.NONE_OPTION" is too complicated [message #607361 is a reply to message #90041] |
Sun, 08 May 2005 12:37 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Found part of your problem. You have dt.jar in your classpath somewhere.
This is Sun's version of the Swing beaninfo, and it conflicts with ours,
but there is no way to override theirs. You don't need it, it has
nothing but beaninfo stuff in it.
That cause the problem with the debugGraphicsOption. After you remove
the jar you will need to do a clean all projects build because we need
to clear out some cached info.
--
Thanks,
Rich Kulp
|
|
|
| Re: IWAV0125E "DebugGraphics.NONE_OPTION" is too complicated [message #607363 is a reply to message #90075] |
Sun, 08 May 2005 15:00 |
| Eclipse User |
|
|
|
In article <d5lfll$pf0$1@news.eclipse.org>, richkulp@us.NO_SPAM.ibm.com
says...
> Found part of your problem. You have dt.jar in your classpath somewhere.
> This is Sun's version of the Swing beaninfo, and it conflicts with ours,
> but there is no way to override theirs. You don't need it, it has
> nothing but beaninfo stuff in it.
>
> That cause the problem with the debugGraphicsOption. After you remove
> the jar you will need to do a clean all projects build because we need
> to clear out some cached info.
Great catch! Did have the dt.jar in for the legacy reason that it
contains the SwingBeanInfo.class (but, it has been dropped as of Java 5,
so I had pulled the class out anyway - just did not think to remove the
jar).
Everything is now working as expected.
Thanks again.
|
|
|
| Re: IWAV0125E "DebugGraphics.NONE_OPTION" is too complicated [message #607364 is a reply to message #90104] |
Sun, 08 May 2005 15:22 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Actually I'm glad you came up with this problem! A few weeks ago I was
tearing my hair out working with another person getting a similar error.
But I couldn't track it down. In her case it was a property that we had
supplied an enumeration for and I couldn't see how our BeanInfo could
come up bad like that.
Your case was the key to finding the problem because for you it was
debugGraphicsOption. We don't even provide an enumeration for that
property! So that clued me in to there being another BeanInfo and I was
able to track it down to dt.jar then. Thanks!
Gerald Rosenberg wrote:
> In article <d5lfll$pf0$1@news.eclipse.org>, richkulp@us.NO_SPAM.ibm.com
> says...
>
>>Found part of your problem. You have dt.jar in your classpath somewhere.
>>This is Sun's version of the Swing beaninfo, and it conflicts with ours,
>> but there is no way to override theirs. You don't need it, it has
>>nothing but beaninfo stuff in it.
>>
>>That cause the problem with the debugGraphicsOption. After you remove
>>the jar you will need to do a clean all projects build because we need
>>to clear out some cached info.
>
>
> Great catch! Did have the dt.jar in for the legacy reason that it
> contains the SwingBeanInfo.class (but, it has been dropped as of Java 5,
> so I had pulled the class out anyway - just did not think to remove the
> jar).
>
> Everything is now working as expected.
>
> Thanks again.
--
Thanks,
Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.04895 seconds
Home