- This topic has 32 replies, 4 voices, and was last updated 20 years, 2 months ago by
.
-
Posts
-
Hi,
We have been using Eclipse 2.12 and MyEclipse 2.8 for the last number of months and have been very, very happy with the software and the support – y’all are great! And I am going to need some more of your help, once again. We are moving to Eclipse 3.0 and, therefore, MyEclipse 3.8. I am not sure if my questions lie in the realm of Eclipse or MyEclipse so I must apologize ahead of time! I installed Eclipse 3.0 and MyEclipse 3.8. I added the quickfix 3. I then imported my existing Eclipse 2 projects into the new Eclipse workspace. There are three standard java projects – util, resource and model and one standard web project – web.
—After I imported my projects, I noticed that they each have different builders! Is there some place that discusses these builders?
project util – Java Builder, Structured Document and Model Builder
project model – Java Builder, Structured Document and Model Builder, Validation
project resource – Java Builder, Structured Document and Model Builder
project web – WebClassPathBuilder, Java Builder, J2EEProjectValidator, DeploymentDescriptorValidator, NOP JSP Builder, Deployment Builder, Structured Document and Model Builder, Validation—After I do a build, I get the following warning in the task list (it doesn’t happen in the 2.0 Eclipse/MyEclipse) and I was hoping for some advice on how to investigate it?
IWAE0010E Run-time exception java.lang.ExceptionInInitializerError occurred during validation. The validator being run was JSP Validator and the message thrown was . web August 31, 2004 2:07:36 PM—The last question is part of another thread which I started, but I might as well ask it here – I hope that you don’t mind! I am not seeing the smart deploy work for jars which are in supporting projects. For instance, there are several jars which are in the util project which not referenced in any other project. The web project, depends upon the util project. When I deploy, the util classes are correctly copied over (how cool is this!), but the jar files in the lib are not. Is there something special that I need to do in order to get this working?
Thanks,
James
PS just to let you know – it seems that the emoticons are not working either :cry:[/b]
We have been using Eclipse 2.12 and MyEclipse 2.8 for the last number of months and have been very, very happy with the software and the support – y’all are great
Thank you for the support, you have a lot of choices out there and we appreciate you choosing us!
I am not sure if my questions lie in the realm of Eclipse or MyEclipse so I must apologize ahead of time! I installed Eclipse 3.0 and MyEclipse 3.8. I added the quickfix 3.
Do you really mean MyEclipse 3.8.1 or 3.8? If you mean 3.8, then the quick fixes will likely break your install as they are intended only for 3.8.1.
–After I imported my projects, I noticed that they each have different builders! Is there some place that discusses these builders?
I would expect the builders for all the Java Projects to be the same, which is weird that there is a validation builder tacked on the end of the model project. Do you have validation disabled for the other two projects?
The builders are just Eclipse components that are in charge of handling different stages of “building” a project (Project > Build). They run in the order they are listed. Some handle the compiling, other handles the validation, deployment update, stuff like that. If you would like more details, let me know and I can ask a dev (if they have time) to reply.
–After I do a build, I get the following warning in the task list (it doesn’t happen in the 2.0 Eclipse/MyEclipse) and I was hoping for some advice on how to investigate it?
Before we tackel this lets make sure you are running a good install of Eclipse and MyEclipse from my questions above.
The web project, depends upon the util project. When I deploy, the util classes are correctly copied over (how cool is this!), but the jar files in the lib are not.
The JARs in the util projects are not deployed, or the JARs in the web project iself are not deployed? If you want the util project’s libs to deploy you will need to add them via “external jar” to the web project, and set the deployer to deploy them. Because there is no standard lib location for JARs in a Java Project, we can’t automatically deploy them for you.
Or are you talking about the JARs in the Web project iself aren’t deploying? I think we had a bug related to this in the early 3.8 builds, this might be fixed by a quick fix as I’m not aware of anyone having a problem with this.
PS just to let you know – it seems that the emoticons are not working either :cry:[/b]
No worries, I think we disabled them for now.
I am not sure if my questions lie in the realm of Eclipse or MyEclipse so I must apologize ahead of time! I installed Eclipse 3.0 and MyEclipse 3.8.
I added the quickfix 3.Do you really mean MyEclipse 3.8.1 or 3.8? If you mean 3.8, then the quick fixes will likely break your install as they are intended only for 3.8.1.
Yes, it was MyEclipse 3.8.1
–After I imported my projects, I noticed that they each have different builders! Is there some place that discusses these builders?
I would expect the builders for all the Java Projects to be the same, which is weird that there is a
validation builder tacked on the end of the model project. Do you have validation disabled for the other two projects?The builders are just Eclipse components that are in charge of handling different stages of “building” a project (Project > Build). They run in the order they are listed. Some handle the compiling, other handles the validation, deployment update, stuff like that. If you would like more details, let me know and I can ask a dev (if they have time) to reply.
Validation is set to JSP and DTD. All four projects are java projects. One of the projects has some xml schemas and instances – which don’t need to be validated. The web project should have it’s web.xml and struts config file validated. But that is it. This are no EJB’s (EAR) in this app – just a simple war file. While I can guess at some of the builder’s
jobs, is there anyplace which describes what they are actually doing. If you can clarify or send me to a url, it would be greatly appreciated. This is the full set that we have:
Java Builder, Structured Document and Model Builder, WebClassPathBuilder, J2EEProjectValidator, DeploymentDescriptorValidator, NOP JSP Builder, Deployment Builder, Validation–After I do a build, I get the following warning in the task list (it doesn’t happen in the 2.0 Eclipse/MyEclipse) and I was hoping for some advice on how to investigate it?
Before we tackel this lets make sure you are running a good install of Eclipse and MyEclipse from my questions above.
OK – but can you give me some input on this error:
IWAE0010E Run-time exception java.lang.ExceptionInInitializerError occurred during validation. The validator being run was JSP Validator and the message thrown was . web August 31, 2004 2:07:36 PMThe web project, depends upon the util project. When I deploy, the util classes are correctly copied over (how cool is this!), but the jar files in the lib are not.
The JARs in the util projects are not deployed, or the JARs in the web project iself are not deployed? If you want the util project’s libs to deploy you will need to add them via “external jar” to the web project, and set the deployer to deploy them. Because there is no standard lib location for JARs in a Java Project, we can’t automatically deploy them for you.
Or are you talking about the JARs in the Web project iself aren’t deploying? I think we had a bug related to this in the early 3.8 builds, this might be fixed by a quick fix as I’m not aware of anyone having a problem with this.
So, we either need to put the libs directly in into the web app (as external jars) or write an ant script to move them. The problem with the former is that the jars may not be needed by the web project (e.g., for JUnit tests), but are needed by the deployed web app. This seems to decrease encapsulation. May I recommend a MyEclipse web app preference to correlate a lib directory for the dependent projects. Regardless, this is really super!
If you can clarify or send me to a url, it would be greatly appreciated. This is the full set that we have:
Java Builder, Structured Document and Model Builder, WebClassPathBuilder, J2EEProjectValidator, DeploymentDescriptorValidator, NOP JSP Builder, Deployment Builder, ValidationI have sent a request to the devs to see if someone can reply for you.
IWAE0010E Run-time exception java.lang.ExceptionInInitializerError occurred during validation. The validator being run was JSP Validator and the message thrown was . web August 31, 2004 2:07:36 PM
Is this displayed in a popup occasionally when you open a project? We’ve seen this and besides it being annoying, its harmless. If you rebuild your web project, does validation of the JSP pages work correctly? If so then you can ignore this message. We had some issues with the validators and made some quick fixes to them at the beginning so we might have missed some use cases where it spits out harmless messages. I personally haven’t seen this error and don’t know much about it. If it DOES seem to be breaking things, I will pass it along. if its just being shown to you and doesn’t seem to have any side effect lets hold off on it. The team is focusing on bug fixes and performance for the 3.8.2 release right now so I’m guessing their knock out a fix for it.
So, we either need to put the libs directly in into the web app (as external jars) or write an ant script to move them.
More or less. The “external jar” just links the JARs into the project, it doesn’t put the libs in the web app’s directory structure anywhere… I just wanted to clarify that as it sounded from your sentence that maybe you were worried about the JARs getting duplicated in the web project.
The problem with the former is that the jars may not be needed by the web project (e.g., for JUnit tests), but are needed by the deployed web app.
If the web app needs the JARs at run time, I guess I’m not sure how it doesn’t need them at compile-time them… it seem sto be that linking them via external JARs is what you want here… maybe I’m misunderstanding what these JARs are for?
May I recommend a MyEclipse web app preference to correlate a lib directory for the dependent projects.
Actually this is almost exactly what using External JARs OR setting up a User Library encapsulating those libraries would do, which is why we don’t support that… Eclipse takes care of it for us.
IWAE0010E Run-time exception java.lang.ExceptionInInitializerError occurred during validation. The validator being run was JSP Validator and the message thrown was . web August 31, 2004 2:07:36 PM
Is this displayed in a popup occasionally when you open a project? We’ve seen this and besides it being annoying, its harmless. If you rebuild your web project, does validation of the JSP pages work correctly? If so then you can ignore this message. We had some issues with the validators and made some quick fixes to them at the beginning so we might have missed some use cases where it spits out harmless messages. I personally haven’t seen this error and don’t know much about it. If it DOES seem to be breaking things, I will pass it along. if its just being shown to you and doesn’t seem to have any side effect lets hold off on it. The team is focusing on bug fixes and performance for the 3.8.2 release right now so I’m guessing their knock out a fix for it.
This is just in the problem list – which I try to keep empty. It does not appear to have side effects, but the application is complex and I wanted to make sure that something is not just hiding. Also, we are on a team of 7 developers, so everyone will have this error (when we roll out MyEclipse 3.81/Eclipse 3). I read in another post about this error – but nothing which really described why it appears or what it might mean. For now, I’ll hope that 3.82 fixes it, but if the dev team has any ideas, please let me know.
So, we either need to put the libs directly in into the web app (as external jars) or write an ant script to move them.
More or less. The “external jar” just links the JARs into the project, it doesn’t put the libs in the web app’s directory structure anywhere… I just wanted to clarify that as it sounded from your sentence that maybe you were worried about the JARs getting duplicated in the web project.
The problem with the former is that the jars may not be needed by the web project (e.g., for JUnit tests), but are needed by the deployed web app.
If the web app needs the JARs at run time, I guess I’m not sure how it doesn’t need them at compile-time them… it seem sto be that linking them via external JARs is what you want here… maybe I’m misunderstanding what these JARs are for?
May I recommend a MyEclipse web app preference to correlate a lib directory for the dependent projects.
Actually this is almost exactly what using External JARs OR setting up a User Library encapsulating those libraries would do, which is why we don’t support that… Eclipse takes care of it for us.
Our application is broken into 4 separate projects, each of which have their own set of jars and JUnit tests. There are different dependencies for each project. For instance, we have a util project which uses the jakarta-oro.jar . This jar is on the util project’s class path. The web project is dependent upon the util project and just calls classes in the util project. So, the web project has no need to have any access to the ORO jar (it is not in the web project and the build path for the util project does not have the ORO jar set to be exported). But the application war file does need to have the jar in the WEB-INF/lib directory.
However, it does seem that for us to take advantage of this feature (which I really, really like), we need to add them in as external jars. Pragmatically, this means that the dependent project jars need to be double listed – once with their dependent project and once with the web app as external jars. On a large team, that means that as people add new jars to the dependent project, people have to remember to add them into the web project as external jars. Not really a good scenario as it then implies that I will needa JUnit test case in the web project which looks at all of the dependent applications’ jars files and compare it with the web projects’ jars . Again, just the suggestion that having a way to associate dependent project’s jars with the deployed application and not necessarily with the web project, would be preferable.
Thanks,
JamesJames,
About that error, I’m going to ask someone to look into it because it definately shouldn’t be in the problem view, that’s bad on our part. The reconciler errors we are still working on so i wasn’t too worried about those right now.About the lib suggestion, I think I understand better what you are asking, I’ll pass it by the guys and see what they think.
James,
Scott was kind enough to send me this long email in reply to your build question AND the exception issue, you might want to have a look at the thread he links to:Java Builder – Eclipse’s builder that does Java compiles and indexing
Structured Document and Model Builder – Our builder that builds the internal
models upon which the structured editors (XML, XSD, JSP, etc) work on.
Enables you to use our additional editors in that project.
WebClassPathBuilder – Our builder that updates your classpath when you add
libs to WEB-INF/lib. Can be disabled by preference.
J2EEProjectValidator – Our builder that checks the validity of your J2EE
deployment descriptors
NOP JSP Builder – Our builder that does nothing, but is provided for
backward compatibility. It replaces our old JSP builder whose functionality
is now handled by the Structured Doc builder
Deployment Builder – Our builder that keeps your exploded deployments in
sync when you change stuff
Validation – Our builder that revalidates files on save if you have
validation turned on for that particular artifact type.We already have a bug report in to make the structured builder and
validation builder optional for non-MyEclipse projects.One other thing in the thread – he mentions an ExceptionInInitializer error
reported by the JSP validator. It might be caused by my last post in this
thread:
https://www.genuitec.com/forums/topic/jsp-compiling-seems-disabled/#post-214115Thank you for the update. Y’all are really great and I have such a better handle on what is going no beneath the covers . Also, Scott’s suspicions are correct as I did start with a JRE and not a JDK. I’ll switch it and let you know what happens.
I was able to get the jars deployed by listing them all (again) in the web project as external jars. I also created a library with the jar files and added that to the project – but I guess the deployer does not deploy libraries. One more thought – is there a way to add an ant script or some other script (XDoclet?) to run following deployment?
Thanks for all of the help and insight – you guys rock!
James
but I guess the deployer does not deploy libraries.
Not yet, but it should soon, people keep asking for it as its a very cool feature.
One more thought – is there a way to add an ant script or some other script (XDoclet?) to run following deployment?
Geez… I swear a user posted a howto do this a while back, I *think* it had something to do with adding an External Tool, then adding it to the builder list to run.. maybe you can start there?
Thanks for all of the help and insight – you guys rock!
We appreciate you guys being so understanding while we iron out wrinkles!
I downloaded the latest sdk and started Eclipse with the command line :
C:\ibiIDE\eclipse\eclipse.exe -vm C:\j2sdk1.4.2_05\bin\javaw.exe -clean -vmargs -Xms256m -Xmx256mbut I still have the following error:
Severity Description Resource In Folder Location Creation Time 1 IWAE0010E Run-time exception java.lang.ExceptionInInitializerError occurred during validation. The validator being run was JSP Validator and the message thrown was . webProject September 2, 2004 8:22:51 AMNote that the name of our web project is webProject.
Did I implement this correctly? Any other suggestion? Do you know who (Eclipse, MyEclipse) generates this message?
Quote:
One more thought – is there a way to add an ant script or some other script (XDoclet?) to run following deployment?Geez… I swear a user posted a howto do this a while back, I *think* it had something to do with adding an External Tool, then adding it to the builder list to run.. maybe you can start there?
I’ll go try to hunt this down and look at all posts that deal with external tools. If you come across it, please let me know. If I don’t find it, I’ll post it as another thread.
Thanks for the help,
James
James,
About the Error: is this in your log file, or in a popup that comes up as soon as you startup? I can’t reproduce this locally which bugs me because I’d rather we were ALL seeing the same bugs, they’d be easier to fix that way 😉Do you have Windows XP SP2 installed by chance?
Also about the external tool: I’ll keep my eyes peeled, just did a few quick searches and didn’t find it, but I’ll look again.
With the designer it does, we aren’t aware of any others, but I would just find it curious if none of us can reproduce this (SP1) and James is always seeing this and if he was running SP2 that might shed some light.
On microsoft’s site it has a list of applications effected by SP2, Eclipse was one of those apps.
@support-rkalla wrote:
James,
About the Error: is this in your log file, or in a popup that comes up as soon as you startup? I can’t reproduce this locally which bugs me because I’d rather we were ALL seeing the same bugs, they’d be easier to fix that way 😉Do you have Windows XP SP2 installed by chance?
Also about the external tool: I’ll keep my eyes peeled, just did a few quick searches and didn’t find it, but I’ll look again.
While I would like to blame MS, I am only running regular old XP – not SP2. I see the error in the Problems View in Eclipse 3.0. Your comment made me look at the Eclipse log file. When I compile (clean) all projects, I get the entry at the bottom of this message.
FYI – This looks very similar to a discussion over in the support news group (http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-3699.html).
Thanks,
James!ENTRY com.genuitec.eclipse.wdt.jsp.debug 1 1 Sep 02, 2004 13:59:36.830 !MESSAGE Sep 2, 2004 1:59:36 PM com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler ? SEVERE: Javac exception Error running javac.exe compiler at org.apache.tools.ant.taskdefs.compilers.DefaultCompilerAdapter.executeExternalCompile(DefaultCompilerAdapter.java:452) at org.apache.tools.ant.taskdefs.compilers.JavacExternal.execute(JavacExternal.java:44) at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:942) at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:764) at com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler.?(Unknown Source) at com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler.compile(Unknown Source) at com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler.compile(Unknown Source) at com.genuitec.eclipse.wdt.jsp.jasper.driver.MyEclipseJspC.?(Unknown Source) at com.genuitec.eclipse.wdt.jsp.jasper.driver.MyEclipseJspC.parse(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.JSPValidator.validate(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.ValidateAction$1.run(Unknown Source) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1673) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1693) at com.genuitec.eclipse.wdt.jsp.validation.ValidateAction.validate(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.ValidateAction.run(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.Validator.validate(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.Validator.validateIfNeeded(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.Validator.validate(Unknown Source) at com.ibm.etools.validation.ValidatorLauncher.start(Unknown Source) at com.ibm.etools.validate.ValidationOperation.launchValidator(Unknown Source) at com.ibm.etools.validate.ValidationOperation.internalValidate(Unknown Source) at com.ibm.etools.validate.ValidationOperation.validate(Unknown Source) at com.ibm.etools.validate.ValidationOperation.run(Unknown Source) at com.ibm.etools.validate.ValidationBuilder.performFullBuild(Unknown Source) at com.ibm.etools.validate.ValidationBuilder.performFullBuild(Unknown Source) at com.ibm.etools.validate.ValidationBuilder.build(Unknown Source) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:564) at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615) at org.eclipse.core.runtime.Platform.run(Platform.java:747) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:157) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:229) at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615) at org.eclipse.core.runtime.Platform.run(Platform.java:747) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:232) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:268) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:297) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:155) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:212) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66) Caused by: java.io.IOException: CreateProcess: javac.exe -classpath C:\IbiIDE\eclipse\startup.jar;C:\ibiIDE\workspace\utilities\lib\jakarta-oro-2.0.8.jar;C:\j2sdk1.4.2_03\jre\lib\rt.jar;C:\j2sdk1.4.2_03\jre\lib\sunrsasign.jar;C:\j2sdk1.4.2_03\jre\lib\jsse.jar;C:\j2sdk1.4.2_03\jre\lib\jce.jar;C:\j2sdk1.4.2_03\jre\lib\charsets.jar;C:\j2sdk1.4.2_03\jre\lib\ext\Coroutine4Java.jar;C:\j2sdk1.4.2_03\jre\lib\ext\dnsns.jar;C:\j2sdk1.4.2_03\jre\lib\ext\ldapsec.jar;C:\j2sdk1.4.2_03\jre\lib\ext\localedata.jar;C:\j2sdk1.4.2_03\jre\lib\ext\sunjce_provider.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\jstl.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\standard.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts-el.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-beanutils.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-collections.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-digester.jar;C:\ibiIDE\workspace\workbench\WebRoot\WE? at java.lang.Win32Process.create(Native Method) at java.lang.Win32Process.<init>(Unknown Source) at java.lang.Runtime.execInternal(Native Method) at java.lang.Runtime.exec(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execute.java:808) at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:445) at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:459) at org.apache.tools.ant.taskdefs.compilers.DefaultCompilerAdapter.executeExternalCompile(DefaultCompilerAdapter.java:449) ... 40 more --- Nested Exception --- java.io.IOException: CreateProcess: javac.exe -classpath C:\IbiIDE\eclipse\startup.jar;C:\ibiIDE\workspace\utilities\lib\jakarta-oro-2.0.8.jar;C:\j2sdk1.4.2_03\jre\lib\rt.jar;C:\j2sdk1.4.2_03\jre\lib\sunrsasign.jar;C:\j2sdk1.4.2_03\jre\lib\jsse.jar;C:\j2sdk1.4.2_03\jre\lib\jce.jar;C:\j2sdk1.4.2_03\jre\lib\charsets.jar;C:\j2sdk1.4.2_03\jre\lib\ext\Coroutine4Java.jar;C:\j2sdk1.4.2_03\jre\lib\ext\dnsns.jar;C:\j2sdk1.4.2_03\jre\lib\ext\ldapsec.jar;C:\j2sdk1.4.2_03\jre\lib\ext\localedata.jar;C:\j2sdk1.4.2_03\jre\lib\ext\sunjce_provider.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\jstl.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\standard.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts-el.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-beanutils.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-collections.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-digester.jar;C:\ibiIDE\workspace\workbench\WebRoot\WE? at java.lang.Win32Process.create(Native Method) at java.lang.Win32Process.<init>(Unknown Source) at java.lang.Runtime.execInternal(Native Method) at java.lang.Runtime.exec(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execute.java:808) at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:445) at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:459) at org.apache.tools.ant.taskdefs.compilers.DefaultCompilerAdapter.executeExternalCompile(DefaultCompilerAdapter.java:449) at org.apache.tools.ant.taskdefs.compilers.JavacExternal.execute(JavacExternal.java:44) at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:942) at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:764) at com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler.?(Unknown Source) at com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler.compile(Unknown Source) at com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler.compile(Unknown Source) at com.genuitec.eclipse.wdt.jsp.jasper.driver.MyEclipseJspC.?(Unknown Source) at com.genuitec.eclipse.wdt.jsp.jasper.driver.MyEclipseJspC.parse(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.JSPValidator.validate(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.ValidateAction$1.run(Unknown Source) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1673) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1693) at com.genuitec.eclipse.wdt.jsp.validation.ValidateAction.validate(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.ValidateAction.run(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.Validator.validate(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.Validator.validateIfNeeded(Unknown Source) at com.genuitec.eclipse.wdt.jsp.validation.Validator.validate(Unknown Source) at com.ibm.etools.validation.ValidatorLauncher.start(Unknown Source) at com.ibm.etools.validate.ValidationOperation.launchValidator(Unknown Source) at com.ibm.etools.validate.ValidationOperation.internalValidate(Unknown Source) at com.ibm.etools.validate.ValidationOperation.validate(Unknown Source) at com.ibm.etools.validate.ValidationOperation.run(Unknown Source) at com.ibm.etools.validate.ValidationBuilder.performFullBuild(Unknown Source) at com.ibm.etools.validate.ValidationBuilder.performFullBuild(Unknown Source) at com.ibm.etools.validate.ValidationBuilder.build(Unknown Source) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:564) at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615) at org.eclipse.core.runtime.Platform.run(Platform.java:747) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:157) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:229) at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615) at org.eclipse.core.runtime.Platform.run(Platform.java:747) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:232) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:268) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:297) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:155) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:212) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66) Sep 2, 2004 1:59:36 PM com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler ? SEVERE: Env: Compile: javaFileName=/C:/DOCUME~1/jif16877/LOCALS~1/Temp/myeclipse-jspcc//org/apache/jsp/form\program_jsp.java classpath=C:\ibiIDE\workspace\utilities\lib\jakarta-oro-2.0.8.jar;C:\j2sdk1.4.2_03\jre\lib\rt.jar;C:\j2sdk1.4.2_03\jre\lib\sunrsasign.jar;C:\j2sdk1.4.2_03\jre\lib\jsse.jar;C:\j2sdk1.4.2_03\jre\lib\jce.jar;C:\j2sdk1.4.2_03\jre\lib\charsets.jar;C:\j2sdk1.4.2_03\jre\lib\ext\Coroutine4Java.jar;C:\j2sdk1.4.2_03\jre\lib\ext\dnsns.jar;C:\j2sdk1.4.2_03\jre\lib\ext\ldapsec.jar;C:\j2sdk1.4.2_03\jre\lib\ext\localedata.jar;C:\j2sdk1.4.2_03\jre\lib\ext\sunjce_provider.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\jstl.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\standard.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts-el.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-beanutils.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-collections.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-digester.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-fileupload.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-lang.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-logging.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-validator.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts-legacy.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\jython.jar;C:\ibiIDE\eclipse\plugins\org.junit_3.8.1\junit.jar;C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\activation.jar;C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\javax.servlet.jar;C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\jboss-j2ee.jar;C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\jboss-jaas.jar;C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\jsse.jar;C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\jts.jar;C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\mail.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\bixlaf.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-digester.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts-scaffold_1_1.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-scaffold.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-logging-1.0.3-src.zip;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\fileupload-src.zip;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\strutstest-2.1.2.jar;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\strutstest-212-src.zip;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-beanutils-1.6.1.zip;C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\classes;C:\ibiIDE\workspace\utilities\bin;C:\ibiIDE\workspace\model\bin;C:\ibiIDE\workspace\resource\bin;C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wdt.jsp.debug_3.8.1\lib\jasper-runtime.jar;C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wdt.jsp.debug_3.8.1\lib\jsp-api.jar cp=C:\IbiIDE\eclipse\startup.jar cp=C:\ibiIDE\workspace\utilities\lib\jakarta-oro-2.0.8.jar cp=C:\j2sdk1.4.2_03\jre\lib\rt.jar cp=C:\j2sdk1.4.2_03\jre\lib\sunrsasign.jar cp=C:\j2sdk1.4.2_03\jre\lib\jsse.jar cp=C:\j2sdk1.4.2_03\jre\lib\jce.jar cp=C:\j2sdk1.4.2_03\jre\lib\charsets.jar cp=C:\j2sdk1.4.2_03\jre\lib\ext\Coroutine4Java.jar cp=C:\j2sdk1.4.2_03\jre\lib\ext\dnsns.jar cp=C:\j2sdk1.4.2_03\jre\lib\ext\ldapsec.jar cp=C:\j2sdk1.4.2_03\jre\lib\ext\localedata.jar cp=C:\j2sdk1.4.2_03\jre\lib\ext\sunjce_provider.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\jstl.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\standard.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts-el.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-beanutils.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-collections.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-digester.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-fileupload.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-lang.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-logging.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-validator.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts-legacy.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\jython.jar cp=C:\ibiIDE\eclipse\plugins\org.junit_3.8.1\junit.jar cp=C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\activation.jar cp=C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\javax.servlet.jar cp=C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\jboss-j2ee.jar cp=C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\jboss-jaas.jar cp=C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\jsse.jar cp=C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\jts.jar cp=C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.j2eedt.core_3.8.1\data\libraryset\1.3\mail.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\bixlaf.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-digester.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\struts-scaffold_1_1.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-scaffold.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-logging-1.0.3-src.zip cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\fileupload-src.zip cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\strutstest-2.1.2.jar cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\strutstest-212-src.zip cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\lib\commons-beanutils-1.6.1.zip cp=C:\ibiIDE\workspace\workbench\WebRoot\WEB-INF\classes cp=C:\ibiIDE\workspace\utilities\bin cp=C:\ibiIDE\workspace\model\bin cp=C:\ibiIDE\workspace\resource\bin cp=C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wdt.jsp.debug_3.8.1\lib\jasper-runtime.jar cp=C:\ibiIDE\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wdt.jsp.debug_3.8.1\lib\jsp-api.jar work dir=C:\DOCUME~1\jif16877\LOCALS~1\Temp\myeclipse-jspcc extension dir=C:\Program Files\Java\j2re1.4.2_03\lib\ext srcDir=C:\DOCUME~1\jif16877\LOCALS~1\Temp\myeclipse-jspcc compiler=extJavac include=org/apache/jsp/form/program_jsp.java !ENTRY com.ibm.etools.validation 4 0 Sep 02, 2004 13:59:38.282 !MESSAGE *** ERROR ***: Thu Sep 02 13:59:38 EDT 2004 java.lang.ExceptionInInitializerErrorHrrm it looks like you are running out of environment space when it tried to execute too long of a command to compile the page… a real test would be to install Eclipse to C:\Eclipse, and put your workspace in C:\Eclipse\workspace and then try it…. but I realie this could be a huge PIA.
Can you try removing extraneous libraries from your classpath? Maybe that library set if you don’t need it, and instead add the jsp-api.jar and servlet-api.jar files from your Tomcat install?
This is a known problem with Windows in general, sometimes when you install Tomcat to C:\Program Files\Apache Group\Tomcat 5.0 which is its default, it can’t start up either because it tries to build its classpath via FQ path names for the JARs and the command just gets too long for the windows shell to execute…
