Community
Participate
Working Groups
I've successfully installed this release before on my machine. Since then I installed Tomcat 4.1 and Cocoon 2.0 (2.0.2?) which both work. Unfortunately, Eclipse would not, so I reinstalled it. Now Eclipse will not complete the installation sequence (tells me to look at .log): I won't repeat the log list here because it is almost identical to the following: http://dev.eclipse.org/newslists/news.eclipse.tools/msg26721.html (The top level exceptions (10 or so) are identical.) Documentation for Cocoon indicates it needs a later release of the JDK (Sun's) because Cocoon uses a later release of Xerces (xerces-1.4.4.jar) and Xalan (xalan-2.2.0-D13.jar). (These have been placed in ...\jre\lib\endorsed along with the xml-apis.jar file.) The top level message in the (Eclipse .log) file indicates that InitializeParser failed. My questions are reasonably simple (although I suspect the answers are not): 1) How do I configure Eclipse to use the newer versions of Xerces and Xalan? 2) Will this fix the problem or is something else going on? When responding keep in mind that I have little experience with Java (I'm trying to "port" a large Perl app to Cocoon and need to build custom components, i.e., I need a JDE badly.) NOTE: Migration to Java-based solution is dead in the water till this issue is resolved. Thanks in advance. P.S. Answer to this problem may help Feng Zhou also (problem listed above).
Eclipse currently ships with its own version of Xerces, on which runtime and several other plug-ins rely on. There is a known issue with running Eclipse with other version of Xerces in the boot classpath (see bug 19252, bug 37696). Please try to run eclipse without using the libraries in ext/lib and let us know if it works: eclipse -vmargs -Djava.ext.dirs=
Closing as a duplicate. Problem is conflicting xerces installed with other tools. *** This bug has been marked as a duplicate of 36643 ***
(from originators message) At any rate I tried the suggestion: eclipse -vmargs -Djava.ext.dirs= It did not work this way or when I also specified the location of the JVM (using -vm)--same problem Eclipse would not finish the install. Since this bug was tied 36643 which indicated one of the common problems was use of JRE\lib\endorsed as the location for Xerces, I just changed the name of the directory to 'E' and tried to complete the install. It worked and I was able to create a project. If I change 'E' back to 'endorsed', Eclipse will start up but some of the plugins (like Welcome) fail and some indicate parse errors. No surprise. I'm still dead in the water right now as Cocoon 2.0 requires the newer release of Xerces (in 'endorsed') and this causes problems with Eclipse. Is anyone working this or should I switch to another JDE? Thanks in Advance. Jon P.S. Hope this helps.
A recent suggestion (by a knowledgable friend) provided temporary relief from the problem... In my case I'm trying to build custom components for Cocoon 2.0 which requires a later version of Xerces than that used by Eclipse. I installed Tomcat, Cocoon, and Eclipse in that order only to encounter the "Eclipse won't install bug". My form of the bug was caused by placing the Xerces, Xalan, XML-apis jars in lib/endorse subdirectory of the Java runtime. What fixed the problem for me was relocating the offending JARs from the Java Runtime's lib/endorsed to Tomcat's lib/endorsed. The Eclipse install then completed without error and both Tomcat and Cocoon appear to work correctly. To use the correct version of Xerces to build components for Cocoon, the Eclipse project must be setup so the classpath includes the version of Xerces's from the Java runtime's lib\endorsed directory. So far this has worked just fine. The reason this provides temporary relief is that it allows you to continue development for Cocoon, but Tomcat is probably not the runtime environment for a production application. (Typically JBoss or some other Java server platform is used--so I'm told.) Eventually, users of this workaround will have to find the appropriate fix for their production platform. NOTE: I'm an new to Java and Java related technology, so you may want to verify this repair with others who have a few more miles under their belt.
