PDA

View Full Version : Error parsing the project - NullPointerException



goahead
04-15-2003, 07:26 PM
I have started adding a new java bean to my project and all of a sudden I am getting this error when I either try to build the project from the commandline, or when I try to open the project in the UI.

Here is the error I am getting:
Initializing InstallShield MultiPlatform 5.0...
Searching for Java(tm) Virtual Machine...
Verifying Java 1.4.0 by Sun Microsystems
.
Verifying Java 1.4.0 by Sun Microsystems
.......
Running InstallShield MultiPlatform 5.0...
java.lang.NullPointerException
at com.installshield.qjml.QProperty.writeToParent(QProperty.java:288)
at com.installshield.wizard.qjml.QWizardBeanPropertyAccess.add(QWizardBe
anPropertyAccess.java:46)
at com.jxml.quick.tf.QClassWrapper.add(QClassWrapper.java:111)
at com.jxml.quick.engine.QElementFactory$QElement$EState.processEnd(QEle
mentFactory.java:284)
at com.jxml.quick.engine.QCMFactory$QCM.endElement(QCMFactory.java:112)
at com.jxml.quick.engine.QContextImpl.endElement(QContextImpl.java:54)
at com.jxml.quick.QConvert.endElement(QConvert.java:114)
at com.installshield.isje.project.QProjectHandler.endElementImpl(QProjec
tHandler.java:53)
at com.installshield.isje.project.ProjectHandler.endElement(ProjectHandl
er.java:50)
at com.sun.xml.parser.Parser.maybeElement(Parser.java:1413)
at com.sun.xml.parser.Parser.content(Parser.java:1499)
at com.sun.xml.parser.Parser.maybeElement(Parser.java:1400)
at com.sun.xml.parser.Parser.content(Parser.java:1499)
at com.sun.xml.parser.Parser.maybeElement(Parser.java:1400)
at com.sun.xml.parser.Parser.content(Parser.java:1499)
at com.sun.xml.parser.Parser.maybeElement(Parser.java:1400)
at com.sun.xml.parser.Parser.content(Parser.java:1499)
at com.sun.xml.parser.Parser.maybeElement(Parser.java:1400)
at com.sun.xml.parser.Parser.content(Parser.java:1499)
at com.sun.xml.parser.Parser.maybeElement(Parser.java:1400)
at com.sun.xml.parser.Parser.parseInternal(Parser.java:492)
at com.sun.xml.parser.Parser.parse(Parser.java:284)
at com.installshield.isje.project.ProjectParser.parse(ProjectParser.java
:16)
at com.installshield.isje.project.ProjectIO.read(ProjectIO.java:154)
at com.installshield.isje.commandline.CommandLineProcessor.openProject(C
ommandLineProcessor.java:336)
at com.installshield.isje.commandline.CommandLineProcessor.processComman
dLineArguments(CommandLineProcessor.java:226)
at com.installshield.isje.ISJE.main(ISJE.java:100)
A error occurred parsing the project. (com.jxml.quick.QPE: java.lang.NullPointer
Exception)

[1] + Done(134) ?
3420 Abort ismpc.exe

Any suggestions would be helpful.

hbarakat
04-16-2003, 01:23 PM
I am having a similar problem on Linux.
But when I try to open the project I get:

A error occured parsing the project. (com.jxml.quick.QPE: An error occured creating the bean info for class com.installshield.project.wizardbeans.InstallCheckPanel: java.lang.Error)

A friend of mine opens the self-same project though without any trouble, so I'm thinking something screwy is going on...

help...I'm stuck! :-(

William
04-18-2003, 01:44 PM
With respect to the second posting, does it really say "com.installshield.project.wizardbeans.InstallCheckPanel"? If so, then the package name is incorrect. Have you been manually editing the project file by any chance?


With respect to the first posting, could you post the code for the java bean you are added just before the problem started occurring (I'm assuming it is a custom class you are referring to)? Further, could you post any BeanInfo classes you are providing associated with that custom bean?

goahead
04-18-2003, 04:04 PM
I've managed to get around my issue. I just went into the project XML file and clipped out the section refering the my Custom Bean. Then I started the GUI and everything appeared to work correctly.

I *think* I might have changed some properties or some other thing that caused the problem and I still had the GUI open.

I was able to just re-add my Bean and everything has worked fine since then.

hbarakat
04-19-2003, 08:03 AM
although I *haven't* found the answer to my problems yet,
I *did* discover (thanks to a friend) how to manually unregister the custom bean. This is done by removing the appropriate line from the ismp.registry file.