[
https://issues.jboss.org/browse/JBIDE-9287?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-9287:
----------------------------------------------
I have added formal automatic test that checks that class
org.apache.xerces.parsers.SAXParser is in class path of
org.jboss.tools.cdi.seam.config.core plugin. There is no much practical use in this test
now, because instance of SAXParser is created by constructor, not by factory.
To reproduce this issue in JBDS 3.2.0, one could try the following.
1. Add a plugin to JBDS that does not deal with xml and that declares some simple view X.
Plugin activator should run code
{code}
try {
XMLReaderFactory.createXMLReader("org.apache.xerces.parsers.SAXParser");
} catch (Exception e) {
}
{code}
2. Open Eclipse, close everything in it, then open Resource perspective and open view X in
it.
3. Close/Open Eclipse, make sure that view X is open.
4. Switch to Web Development perspective and try working with CDI project with config
extension (see org.jboss.tools.cdi.seam.config.core.test/projects/CDIConfigTest).
These steps increase probability, that XMLReaderFactory will be loaded with class loader
that has no SAXParser in its class path. If it happens, the issue is reproduced.
NullPointerException in
org.jboss.tools.cdi.seam.config.core.xml.SAXParser
--------------------------------------------------------------------------
Key: JBIDE-9287
URL:
https://issues.jboss.org/browse/JBIDE-9287
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.M2
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M3
java.lang.NullPointerException
at
org.jboss.tools.cdi.seam.config.core.xml.SAXParser.parse(SAXParser.java:66)
at
org.jboss.tools.cdi.seam.config.core.scanner.SeamDefinitionBuilder.createDefinition(SeamDefinitionBuilder.java:71)
at
org.jboss.tools.cdi.seam.config.core.CDISeamConfigExtension.buildDefinitions(CDISeamConfigExtension.java:118)
at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:201)
at
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira