Community
Participate
Working Groups
The following program does not compile inside eclipse. dbf.setXIncludeAware fails. Outside eclipse I can compile with no problem. I'm using IBM Java 1.6 SR7 on Centos 5.4 x86_64 to run eclipse and have no other JVM's. Eclipse is running under this jvm import javax.xml.parsers.*; public class junk { public void foo() { javax.xml.parsers.DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance(); dbf.setXIncludeAware(true); } } -- Configuration Details -- Product: Eclipse 1.2.2.20100122-1337 (org.eclipse.epp.package.java.product) Installed Features: org.eclipse.jdt 3.5.2.r352_v20100108-7r88FEwFI0WTuoBl0iaG0tyhfZH6
Please provide the build path used inside Eclipse.
This looks like a configuration issue. I don't have the same configuration, so it is difficult to try your case. Please provide screenshots of the build path of your project.
OK, I've created a project with only the test and that compiles correctly. The problem was in Solr 1.4 which had the following jar in the path: xml-apis-1.0.b2.jar
Does xml-apis-1.0.b2.jar contain the method you are looking for? If it is added first on the classpath, it might hide types that contain the proper API. If you can compile fine on the command line, always check that you are using the "same" classpath on both sides (the IDE and the command line). So closing as INVALID ?
(In reply to comment #4) > Does xml-apis-1.0.b2.jar contain the method you are looking for? > If it is added first on the classpath, it might hide types that contain the > proper API. It hadn't occurred to me that the core library was being overridden. > If you can compile fine on the command line, always check that you are using > the "same" classpath on both sides (the IDE and the command line). > So closing as INVALID ? Yes, you can close it. Sorry for the noise.
Closing as INVALID.
Verified by reporter