| ExceptionInInitializer Error: class IWAV0189E unknown [message #52785] |
Fri, 30 July 2004 20:57  |
Eclipse User |
|
|
|
Originally posted by: none.nobody.com
I am trying out VE 1.0M2 and figured I'd see what happened when I opened
up one of my existing (non-VE) classes that extends JPanel.
I get the ExceptionInInitializerError (IWAV0118E Class IWAV0189E unknown
(or one of its superclasses) is not found or has errors) and the JavaBeans
view shows my class with a red X in it.
I'm new to VE and thought I'd try it out to see how it compares to
Netbeans' Form Editor.
Is it impossible to use VE with existing "visual classes", or is it only
good for classes that were initially created with VE?
Thanks
|
|
|
| Re: ExceptionInInitializer Error: class IWAV0189E unknown [message #52846 is a reply to message #52785] |
Fri, 30 July 2004 22:48  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
As long as your coding pattern matches the pattern that VE understands,
which is general one, it should work. However the error you are getting
indicates that one of your super classes had an error trying to be
created. First try looking at the .metadata/.log file to see if there is
a log message with the stack trace of why your superclass couldn't be
instantiated. This is typically due to things like trying access a
resource bundle that doesn't exist in an initialization block, or some
other check that you are doing that fails because you are running in a
design time environment (missing resources, missing initialization that
is normally done by a main application which we don't run in the ve, ...)
--
Thanks, Rich Kulp
|
|
|
| Re: ExceptionInInitializer Error: class IWAV0189E unknown [message #596200 is a reply to message #52785] |
Fri, 30 July 2004 22:48 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
As long as your coding pattern matches the pattern that VE understands,
which is general one, it should work. However the error you are getting
indicates that one of your super classes had an error trying to be
created. First try looking at the .metadata/.log file to see if there is
a log message with the stack trace of why your superclass couldn't be
instantiated. This is typically due to things like trying access a
resource bundle that doesn't exist in an initialization block, or some
other check that you are doing that fails because you are running in a
design time environment (missing resources, missing initialization that
is normally done by a main application which we don't run in the ve, ...)
--
Thanks, Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.03717 seconds
] 
Search
Help
Register
Login
Home
