facebook

JSP fails to compile under my user is, but passes as root

  1. MyEclipse IDE
  2.  > 
  3. Java EE Development (EJB, JSP, Struts, XDoclet, etc.)
Viewing 15 posts - 1 through 15 (of 19 total)
  • Author
    Posts
  • #250802 Reply

    fparrott
    Member

    Hi,
    I have a stange problem, that I just can’t understand. I’m using eclipse3.1.2, Myeclipse 4.1.0 (I have tried 4.1.1), jdk1.5, tomcat5.5.12. Under my user id, the app will fail to compile, during auto-build, or when I checkout the project. The package explorer doesn’t show any error markers. However, if I log in as root user, and checkout the same web app, it builds sucessful, and I can deploy it to tomcat, and access it.

    I think I have an environment issue, but have no idea where to start looking. I’ve tried setting (chmod 777) some file paths, but not sure if this the right track.

    In my workspace/.metadata/.log, I see a “Compile failed; see the compiler error output for details.” Is there a log file some where I find the compiler output?

    It said it fails in this file, but no line number is given:
    Apr 19, 2006 8:34:58 PM com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler ?
    SEVERE: Env: Compile: javaFileName=/tmp/myeclipse-jspcc//org/apache/jsp/view_005fquotes_jsp.java

    Any ideas what I’m missing?
    Thanks,
    frank

    !ENTRY com.genuitec.eclipse.wdt.jsp.debug 1 1 2006-04-19 20:34:58.457
    !MESSAGE Apr 19, 2006 8:34:58 PM com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler ?
    SEVERE: Javac exception
    Compile failed; see the compiler error output for details.
    at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:933)
    at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:757)
    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:1721)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1741)
    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(ValidatorLauncher.java:58)
    at com.ibm.etools.validate.ValidationOperation.launchValidator(ValidationOperation.java:1275)
    at com.ibm.etools.validate.ValidationOperation.internalValidate(ValidationOperation.java:1099)
    at com.ibm.etools.validate.ValidationOperation.validate(ValidationOperation.java:1014)
    at com.ibm.etools.validate.ValidationOperation.run(ValidationOperation.java:731)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1721)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1741)
    at com.ibm.etools.validate.ui.ValidationMenuAction.checkProjectConfiguration(ValidationMenuAction.java:397)
    at com.ibm.etools.validate.ui.ValidationMenuAction.performValidation(ValidationMenuAction.java:358)
    at com.ibm.etools.validate.ui.ValidationMenuAction.validate(ValidationMenuAction.java:305)
    at com.ibm.etools.validate.ui.ValidationMenuAction$2.run(ValidationMenuAction.java:249)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1721)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1741)
    at com.ibm.etools.validate.ui.plugin.RunnableWithProgressWrapper.run(RunnableWithProgressWrapper.java:73)
    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)

    Apr 19, 2006 8:34:58 PM com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler ?
    SEVERE: Env: Compile: javaFileName=/tmp/myeclipse-jspcc//org/apache/jsp/view_005fquotes_jsp.java
    classpath=/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/rt.jar:/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/jsse.jar:/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/jce.jar:/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/charsets.jar:/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/ext/localedata.jar:/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/ext/dnsns.jar:/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/ext/sunjce_provider.jar:/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/ext/sunpkcs11.jar:/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/javax.servlet.jar:/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/activation.jar:/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/jboss-j2ee.jar:/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/jboss-jaas.jar:/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/jsse.jar:/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/jts.jar:/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/mail.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/batik-awt-util.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/batik-dom.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/batik-svggen.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/batik-util.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/batik-xml.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/cewolf.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-beanutils.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-collections.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-digester.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-fileupload.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-lang.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-logging.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-validator.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/dom.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jakarta-oro.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jaxen-full.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jaxp-api.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jcommon-0.8.0.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jdbc2_0-stdext.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jfreechart-0.9.8-demo.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jfreechart-0.9.8.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jstl.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/mail.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/sax.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/saxpath.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/standard.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/struts-legacy.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/struts.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/xalan.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/xercesImpl.jar:/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/classes:/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.wdt.jsp.debug_4.1.0/lib/jasper-runtime.jar:/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.wdt.jsp.debug_4.1.0/lib/jsp-api.jar
    cp=/opt/jive/packages/eclipse/current/startup.jar
    cp=/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/rt.jar
    cp=/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/jsse.jar
    cp=/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/jce.jar
    cp=/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/charsets.jar
    cp=/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/ext/localedata.jar
    cp=/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/ext/dnsns.jar
    cp=/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/ext/sunjce_provider.jar
    cp=/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/ext/sunpkcs11.jar
    cp=/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/javax.servlet.jar
    cp=/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/activation.jar
    cp=/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/jboss-j2ee.jar
    cp=/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/jboss-jaas.jar
    cp=/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/jsse.jar
    cp=/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/jts.jar
    cp=/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.j2eedt.core_4.1.0/data/libraryset/1.3/mail.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/batik-awt-util.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/batik-dom.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/batik-svggen.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/batik-util.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/batik-xml.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/cewolf.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-beanutils.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-collections.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-digester.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-fileupload.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-lang.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-logging.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/commons-validator.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/dom.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jakarta-oro.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jaxen-full.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jaxp-api.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jcommon-0.8.0.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jdbc2_0-stdext.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jfreechart-0.9.8-demo.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jfreechart-0.9.8.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/jstl.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/mail.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/sax.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/saxpath.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/standard.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/struts-legacy.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/struts.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/xalan.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/lib/xercesImpl.jar
    cp=/users/fparrott/jive/eclipse/workspace/qotd/ROOT/WEB-INF/classes
    cp=/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.wdt.jsp.debug_4.1.0/lib/jasper-runtime.jar
    cp=/opt/jive/packages/MyEclipse/MyEclipse-4.1.0/eclipse/plugins/com.genuitec.eclipse.wdt.jsp.debug_4.1.0/lib/jsp-api.jar
    work dir=/tmp/myeclipse-jspcc
    extension dir=/opt/jive/packages/jdk/jdk1.5.0_06/jre/lib/ext
    srcDir=/tmp/myeclipse-jspcc
    compiler=extJavac
    include=org/apache/jsp/view_005fquotes_jsp.java

    #250807

    Kapil Kapre
    Member

    Can you run javac from your JDK? (path-to-JDK/bin/javac) with the user account? if not give the user-id execution rights to javac and things should work smoothly.

    #250820

    fparrott
    Member

    HI,
    Yes, I can run (path-to-JDK/bin/javac) from both root and my user account. I checked the “Installed JREs” prefernce, and <path-to-JDK) is the same.

    I’ve discovered the “Run validation: under the Myeclipse context menu. I can recreate the failure with this method.

    Looks like I’m on another wild goose chase… When you quit out of MyEclipse, should /tmp/myeclipse-jspcc get deleted? I found if I launch
    Myeclipse under root account, build the project sucessfully, then quit Myeclipse. Now I launch MyEclipse under my user account. I found this
    time the validation passes, but the response appears immediate. It looks like if there’s a pre-existing /tmp/myeclipse-jspcc, then it uses
    the validation results. If doesn’t appear to re-validate as if it were new. Anyways, under this situation, I can deploy, and run the web app,
    under my user account.

    I’m confused as to which compiler is used. Is the jdk1.5 used or is it Myeclipse jasper?

    can this be some kind of file/directory ownership problem?
    drwxr-xr-x 3 root root 60 Apr 20 10:03 myeclipse-jspcc

    drwxr-xr-x 3 fparrott eng 60 Apr 20 10:08 myeclipse-jspcc

    thanks,
    Frank

    #250821

    Kapil Kapre
    Member

    Validation makes uses of javac so you’re on the right track. Do you have two JDK’s installed? If you’re using a debian based distro try the following command as root

    
    update-alternatives --config java
    

    And select the JDK that you use w/ eclipse as the deafault one.

    #250827

    fparrott
    Member

    hi Kapil,

    Sorry, I should have mentioned. My Linux is an internal version of Red Hat EL 4. We have a wrapper script that launches Eclipse as follows:
    export JAVA_HOME=/opt/jive/jdk/current
    /opt/jive/bin/current/eclipse -showlocation $@

    The JAVA_HOME is pointing to jdk1.5.2_06

    I’m starting to wonder if a have $PATH variable issue too. But in eclipse I have the Installed JREs preference set to the same path as JAVA_HOME.

    What path does MyEclipse use for javac?

    NOw from the user account, if I just enter java -version, this the old version of java from /usr/bin/java/, which is soft linked to /usr/lib/jvm/jre-1.4.2-gcj/bin/java.
    The root user calls the same script… I also see j2re1.4.2_06 here /usr/java, but no sdk.

    “And select the JDK that you use w/ eclipse as the deafault one.”
    Sorry I don’t understand this, since I don’t have debian. If I set the JAVA_HOME in the script, shouldn’t MyEclipse pick this?

    Thanks,
    for your help.
    frank

    #250848

    Kapil Kapre
    Member

    Frank,

    “And select the JDK that you use w/ eclipse as the deafault one.”

    The command which you probably missed which gave context to that statement in my earlier post. You have to scroll a bit to the right to see that because an earlier post exceeded some bounds. Doesnt matter.

    My Linux is an internal version of Red Hat EL 4. We have a wrapper script that launches Eclipse as follows:
    export JAVA_HOME=/opt/jive/jdk/current
    /opt/jive/bin/current/eclipse -showlocation $@

    The JAVA_HOME is pointing to jdk1.5.2_06

    I’m starting to wonder if a have $PATH variable issue too. But in eclipse I have the Installed JREs preference set to the same path as JAVA_HOME.

    What path does MyEclipse use for javac?

    NOw from the user account, if I just enter java -version, this the old version of java from /usr/bin/java/, which is soft linked to /usr/lib/jvm/jre-1.4.2-gcj/bin/java.

    Can you try adding this to your script as an eclipse command line parameter -vm /path/to/jdk/bin/java
    Also point the installed JRE’s preference to this same path. AFAIK MyEclipse uses the Java version that is “in-path”.
    While I confirm some specifics w/ the team could you try this and get back?

    Thanks,
    – Kapil

    #250872

    fparrott
    Member

    Hi,

    Sorry about the “wide” text box. I didn’t notice it when copied the exception trace in.

    I launch Eclipse/MyEclipse, and got Help->about. from the about dialog, I select configuration details, and the VM is pointing to what I have
    in JAVA_HOME. Here’s some of the output.
    -clean
    -consolelog
    -vm
    /opt/jive/packages/jdk/current/bin/java
    eclipse.consoleLog=true
    eclipse.product=org.eclipse.sdk.ide
    eclipse.startTime=1145626939157
    eclipse.vm=/opt/jive/packages/jdk/current/bin/java
    eclipse.vmargs=-Xms40m
    -Xmx832m

    As you requested, I started Eclipse/MyEclipse using the -vm option.

    /opt/jive/bin/eclipse -clean -consolelog -vm /opt/jive/packages/jdk/current/bin/java

    I also tried using the direct path to the vm:
    /opt/jive/bin/eclipse -clean -consolelog -vm /opt/jive/packages/jdk/jdk1.5.0_06/bin/java

    Here’s the -vm configuration details from the Eclipse “about” dialog:
    -vm
    /opt/jive/packages/jdk/jdk1.5.0_06/bin/java
    eclipse.consoleLog=true
    eclipse.product=org.eclipse.sdk.ide
    eclipse.startTime=1145627770570
    eclipse.vm=/opt/jive/packages/jdk/jdk1.5.0_06/bin/java
    eclipse.vmargs=-Xms40m
    -Xmx832m

    JSP Validation fails…

    Thanks for your help and patients,
    Frank

    #250876

    Kapil Kapre
    Member

    oops, we should have tried this earlier. I did mention that ME looks up javac in the current path but we never did try if updating the path fixes the issue.
    Add line#2 to your script and see if it works for you. Also try line#2 w/ the direct path too just in case.

    export JAVA_HOME=/opt/jive/jdk/current
    export PATH=$PATH:/opt/jive/jdk/current/bin
    /opt/jive/bin/current/eclipse -showlocation $@

    #250977

    fparrott
    Member

    Hi Kapil,

    I sorry if I didn’t mention this before. The launch script already exports the JAVA_HOME and PATH. Here’s the setup:
    export JAVA_HOME=/opt/jive/packages/jdk/current
    export PATH=$JAVA_HOME/bin:$PATH

    I also tried using the direct path as suggested.

    Same problem, validation fails.

    I don’t know if this problem can be realted to the way this project is setup.

    How does Myeclipse->run validation work? I have 3 JSP files under a ROOT directory. (in this order)
    ROOT/
    META_INF/
    WEB_INF/
    new_quote.jsp
    sample-graph.jsp
    view_quotes.jsp

    This seems strange behaviour to me. If I launch MyEclipse, and checkout the project from CVS.
    MyEclipse autobuilds the project. In the workspace/.metatdata/.log file, I see validation errors on
    sample_graph.jsp, and view_quotes.jsp, but NOT new_quote.jsp.

    This seems to mean that the first jsp file, new_quote.jsp passed valiadtion during the first initial auto-build.
    If I select new_quote.jsp, right-click->MyEclipse->run validation, I get an execption saying the compile failed (as first reported
    in this thread.) However, the “Progress Information” dialog says “Validation completed”, and under Status:
    “Validation of resource /qotd/ROOT/new_quote.jsp is complete.”

    WHY doesn’t the “Progress Information” dialog show that compile has failed????? This seens to imply a sucess.

    I can’t determine if this behaviour is entirely environmental…

    thanks for the help,
    Frank

    #250978

    Riyad Kalla
    Member

    Frank,
    Are you using a trial version of MyEclipse? If so, do you have Eclipse/MyEclipse installed as *separate* users? This can cause licensing problems for the trial version under Linux, with a subscription the licensing problems don’t exist (although I’m not suggesting if you buy a license the problem fixes itself, just pointing something out).

    Also, try and reinstall Eclipse and MyEclipse AS your user UNDER your user account and create a new workspace there as well. Be sure to re-download the Eclipse 3.1.2 SDK and MyEclipse 4.1.1 releases (yes, please redownload even if you have them) and *do not* use existing directories, use new ones. Create a new workspace and create a new web project, create a JSP page and see if that works.

    #250983

    fparrott
    Member

    Hi Riyad,

    No, it’s not trial. Under “Update subscription”, I see my companies subscriber code. We’re a paying customer. What we are doing is developing a toolkit package, where MyEclipse is
    one of the tools we bundle and deliver to our internal developers. There’s a build script we use, and we build eclipse/myeclipse as root user. Myeclipse is installed into a separate directory.
    Granted the MyEclipse subdirectories are owned by root. From within our Eclipse installation and configuration directory, we set a links file back to the MyEclipse extension directory.

    Are there files and directories that should have their permissions set? for example Myeclipse/plugins?

    The workspace is created under the users account. The build script compeletly removes all
    directories, including the separate MyEclipse directory. So the build is always a fresh installation of Eclipse3.1.2. Although we have a local copy of the manual MyEclipse Installation.
    I’ll download that again, build, and see what happens.

    I’ll let know.

    Thanks,
    frank

    #250992

    Riyad Kalla
    Member

    Frank,
    What I would try at this point to rule out any silliness is first:

    1) Redeploy a fresh copy with your script, does it work?

    if not then

    2) Redownload Eclipse 3.1.2 SDK and MyEclipse 4.1.1 (Forgetting your script), and install them both to new dirs, create new workspace and new Web Project and JSP. Did that work?

    Try and figure out at which step things go haywire.

    #251017

    fparrott
    Member

    Hi,

    I’ve done option one serveral time before. no change on the problem.

    I’ve tried your option 2. New workspace, new dirs. Still see the same problem!!!

    I created a new directory within my home. /users/fparrott/myeclipse;
    cd myeclipse, mkdir Myeclipse. In Myeclipse/ I installed the myeclipse manual image.
    Back in /users/fparrott/myeclipse/eclipse, I create a links/ dir. In the links dir, I create link file, with
    path=/user/fparrott/myeclipse/Myeclipse

    I don’t see why creating a links dir would cause this…

    I create a small launch script, as follows:

    #!/bin/bash

    export JAVA_HOME=/opt/jive/packages/jdk/current
    export PATH=/opt/jive/packages/jdk/current/bin:$PATH
    /users/fparrott/myeclipse/eclipse/eclipse -showlocation $@

    command line: sh script -clean -consolelog.

    oh.. also I’m finding I have to change the preference “MyEclipse->validation->Maximum number of validation messages on a project”
    to something higher than 25 (100), before I checkout the qotd project. Otherwise you wont see any failures upon the initial
    autobuild of the project.

    With the new workspace, I check out my qotd appl., during the auto build, I see the validation fails on 2 of 3 jsp files. (see thread abouve for
    fail names.)

    There’s something with the preference “MyEclipse->validation->Maximum number of validation messages on a project”
    If it’s set to 25, and I try to manully validate the JSP, I get:
    “Validation was terminated on qotd because the maximum number of messages were reported.”

    If I set it to 100, then I get the following exceptions:
    !ENTRY com.genuitec.eclipse.wdt.jsp.debug 1 1 2006-04-24 14:44:46.481
    !MESSAGE Apr 24, 2006 2:44:46 PM com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler ?
    SEVERE: Javac exception
    Compile failed; see the compiler error output for details.

    Apr 24, 2006 2:44:46 PM com.genuitec.eclipse.wdt.jsp.jasper.compiler.Compiler ?
    SEVERE: Env: Compile: javaFileName=/tmp/myeclipse-jspcc//org/apache/jsp/view_005fquotes_jsp.java
    classpath=/

    So what the deal with /tmp/myeclipse-jspcc?

    Also with preference “MyEclipse->validation->Maximum number of validation messages on a project” set at 25,
    I don’t see the /tmp/myeclipse-jspcc directory.

    Any ideas?

    Thanks,
    frank

    #251021

    fparrott
    Member

    Hi,

    Could you please tell me what could be causing this behaviour?

    I have “MyEclipse->validation->Maximum number of validation messages on a project” set at 50.

    I launch eclipse/MyEclipse on existing workspace and project.

    from the project, I select the first jsp file, new_quote.jsp. Then I choose “Run validation”. If seems to pass the very first time.
    Now I select the same file again, and “Run Validation”. this time in the Eclipse .log file, the compile fails, and it complains about:
    SEVERE: Env: Compile: javaFileName=/tmp/myeclipse-jspcc//org/apache/jsp/new_005fquote_jsp.java
    classpath=/

    As I’ve said before, why doesn’t this mark any errors on the editor view? The “Progress Information” dialog doesn’t report an error.
    I don’t see any error markers on the right margin.

    Is this a bug? Why would the new-quote.jsp validation fail the second and several attempts thereafter fail?

    Thanks,
    frank

    #251030

    Riyad Kalla
    Member

    Frank,
    The exception in the log file pertaining to the JSP validation is what happens when it cannot find the “javac” Executable in your System PATH. This is not reported in the user interface because it’s not a problem with the file, it’s a problem with MyEclipse successfully executing it’s JSP validator. I have a feeling there is probably nothing wrong with your project and the fact that MyEclipse cannot find javac is just making the validators squirrel, once that happens, you won’t see errors until things clear up.

    Is this project something you can share with us?

Viewing 15 posts - 1 through 15 (of 19 total)
Reply To: JSP fails to compile under my user is, but passes as root

You must be logged in to post in the forum log in