Error free templates produce strange problem: Does not exist

MyEclipse Archived

Bugs

This topic has 14 replies, 6 voices, and was last updated 20 years, 3 months ago by Riyad Kalla.

Viewing 15 posts - 1 through 15 (of 15 total)

Author

Posts
June 18, 2004 at 10:39 am #208751 Reply

posttool
Member

The page compiles and displays correctly with Tomcat but is leaving this message in my problems window. I am using <%@ include statements as well as jstl and my own tags. Thanks. David

Severity Description Resource In Folder Location Creation Time
2 Exception during execution: Resource /SFHIV/.myeclipse/.bje_tmp/templates$/_$0030$0030_home$002ejsp$.java does not exist. – org.eclipse.core.internal.resources.ResourceException: Resource /SFHIV/.myeclipse/.bje_tmp/templates$/_$0030$0030_home$002ejsp$.java does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:310)
at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:178)
at org.eclipse.core.internal.resources.File.getContents(File.java:252)
at org.eclipse.core.internal.resources.File.getContents(File.java:243)
at de.bb.bje.eclipse.IncrementalJspBuilder.compile(Unknown Source)
at de.bb.bje.eclipse.IncrementalJspBuilder.visit(Unknown Source)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
at de.bb.bje.eclipse.IncrementalJspBuilder.?(Unknown Source)
at de.bb.bje.eclipse.IncrementalJspBuilder.build(Unknown Source)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:558)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
at org.eclipse.core.runtime.Platform.run(Platform.java:758)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:154)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:226)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
at org.eclipse.core.runtime.Platform.run(Platform.java:758)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:229)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:265)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:294)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:153)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:207)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
00_home.jsp SFHIV/WebRoot/templates June 17, 2004 1:17:49 PM

June 23, 2004 at 8:51 am #208958 Reply

posttool
Member

HELLO???? CAN SOMEONE AT LEAST GIVE ME A QUICK RESPONSE HERE????

June 23, 2004 at 9:54 am #208966 Reply

support-michael
Keymaster

HELLO???? CAN SOMEONE AT LEAST GIVE ME A QUICK RESPONSE HERE????

OK! Ok! ok .k ….

Is the JSP file that contains an error marker an included JSP, i.e., a fragment or is it a top-level JSP?

1) If yes, then the problem is the JSPCC compiler can’t tell the difference between a fragment and a document. Try changing the fragment’s file suffix to *.jspf or *.jsf

2) If no, then possibly the include file is not being located or something else. At this point we need more info to isolate the problem. For example try a smaller doc with fewer JSP features to see if it can be isolated. If that doesn’t work then please post the file or snippet where the problem may be occurring.

June 23, 2004 at 3:16 pm #209003 Reply
posttool
Member
Thanks for the response! I have isolated the problem.
My pages look something like this:
```
<%@ page language="java" import="java.util.*"%>
<%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %>
<%@ taglib uri="/WEB-INF/dataTaglib.tld" prefix="pt" %>
<pt:permission group="org_sfhiv.org_sfhiv"/>
<pt:pageModel />
<%@ include file="include/head.html" %>
<div id="content">
xxx
</div>  
<%@ include file="include/foot.html" %>  
```
The error occurs because of a nested include. “head.html” looks like this:
```
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
    <base href="<c:out value="${dataGroup.baseURL}"/>">
    <title>SFHIV: <c:out value="${model.meta.displayName}" escapeXml="true"/></title>
    <meta http-equiv="keywords" content="keywords">
    <meta http-equiv="description" content="description">
    <style type="text/css">
        @import url(templates/css/menu.css);
        @import url(templates/css/menu_<c:out value="${model.path[1].index}" />.css);
        @import url(templates/css/<c:out value="${model.meta.style}"/>.css);
    </style>
    <link rel="stylesheet" type="text/css" media="print" href="templates/css/print.css" />
    <c:out value="${include_js}" escapeXml="false"/>
</head>

<body>
    <div id="wrap">
        <div id="bar">[b]<%@ include file="../flash/topBar.html" %>[/b]</div>
        <div id="divider"></div>
        
        <div id="menu">
            <c:forEach var="item" items="${model.path[0].categories}">
                <a href="<c:out value="${dataGroup.baseURL}${item.id}"/>.html" <c:if
                  test="${item.id == model.path[1].id}">id="activelnk"</c:if>><c:out
                    value="${item.displayName}" escapeXml="false" /></a>
            </c:forEach>
        </div>
        <div id="title"><a href="index.html"><img src="templates/images/title.gif"
          alt="HIV Prevention in San Francisco" border="0"/></a></div>
        
        <div id="subtitle"><img
            src="templates/images/menu_<c:out value="${model.path[1].index}" />/overview.gif"
            alt="<c:out value="${model.meta.displayName}"/>" width="280" height="20"/></div>
        <div id="overview">
            [b]<%@ include file="sectionOverviews.html" %>[/b]
        </div>
        <div id="submenu_border">
            <div id="submenu">
                <c:forEach var="pathElement" begin="1" items="${model.path}">
                    <div class="submenu_2">
                        <c:forEach var="item" items="${pathElement.categories}">

                            <c:if test="${item.groupVisibility == 'normal'}">
                            <a href="<c:out value="${dataGroup.baseURL}${item.id}"/>.html" <c:if
                              test="${item.id == model.meta.id || item.id == model.path[2].id}">
                              class="selected"</c:if>><c:out value="${item.displayName}" 
                              escapeXml="false" /></a><br/>
                            </c:if>
                        </c:forEach>
                    </div>
                </c:forEach>
            </div>
        </div>
    </div>
```
The first include cause the failure. When deleted, your software has no problem with my files. The second include is not a problem for it… –

System Setup ——————————-
Operating System and version: WinXP
Eclipse version: 3RC3 (same problem in RC1 & 2)
Eclipse build id: Build id: 200406192000
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: none
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 7 (not including org.eclipse.pde_3)
MyEclipse version: the new beta!
Eclipse JDK version: 1.4.2
Application Server JDK version:
Are there any exceptions in the Eclipse log file?

– Message Body ——————————-
June 23, 2004 at 3:25 pm #209004 Reply

posttool
Member

Ahhhh. I am continuing to narrow… It seems that a nested jstl set causes the failure.
In the ../flash/topBar.html there is this:

<c:set var=”topBarUrl”
value=”templates/flash/topBar.swf?colorCode=${model.meta.path[1].index}” scope=”page”

/>

I have to remove this line completely to remove the error (from myeclipse) – again it compiles in tomcat and serves properly. But after trying to move the line it to the top level jsp as well as the 1st include, I find that I cannot get your jsp compiler to stop complaining. Thanks again.
David

June 23, 2004 at 9:03 pm #209005 Reply

Scott Anderson
Participant

<c:set var=”topBarUrl”
value=”templates/flash/topBar.swf?colorCode=${model.meta.path[1].index}” scope=”page”

/>

Well, that explains it. You’re using JSP 2.0 expression syntax and our compiler does not yet support it. Until we roll out JSP 2.0 support (soon), I’d suggest that you turn off JSP compilation in the MyEclipse preferences to avoid this type of issue in the future.

June 24, 2004 at 1:38 am #209007 Reply

No Operation
Member

Dont agree: JSP 2.0 expression language does no harm to JSP1.2 pages.

AND: the statements are working on my system (Eclipse3Rc3 + latest MyEclipse) without any error.

NOP

June 24, 2004 at 7:18 am #209015 Reply

Riyad Kalla
Member

posttool, what is your system info? Eclipse/MyEclipse/JDK/Tomcat versions?

June 24, 2004 at 9:45 am #209029 Reply

posttool
Member

Eclipse 3RC3 build 200406192000
MyEclipse Version: 3.7.101 Build id: 200405301200-3.8-Beta1
Java version “1.4.2_03”
Tomcat 5 (JWSDP-1.3)

It does seem funny – All of the other EL is obviously unevaluated… Why this?
JSP compilation is now OFF.

June 24, 2004 at 9:48 am #209030 Reply

posttool
Member

PS. Who is the woman on your home page? And why is the woman on your home page? Is she a lead developer at myeclipse? Is she your spokesperson? Please ignore this question. I just see her often and I woke up too early this morning.

June 24, 2004 at 3:23 pm #209044 Reply

posttool
Member

Ok. I have set the extention of all my includes to .jsf and the jsp compiler behavior is more predictable.

It seems a little counter intuitive to use the extention when I am not using jsf… Thanks for the help.
David

June 24, 2004 at 3:36 pm #209048 Reply

Riyad Kalla
Member

David,
Per the Sun naming guidelines, you should use jspf, not jsf (for the exact reason you stated). Not that calling them jsf is going to break anything, its just ‘good practice’, kind of like well-named getters and setters.

Here is the document: http://java.sun.com/developer/technicalArticles/javaserverpages/code_convention/, the first section addresses file naming. Its actually an interesting read.

June 25, 2004 at 1:43 pm #209086 Reply

posttool
Member

That is a good article.
Thank you for the follow up information Riyad.
Best, David

July 29, 2004 at 5:18 pm #211154 Reply

RickHigh
Member

I am having this same problem with one file. I remove all of the JSP 2.0 standalone expressions, and uses <c:out/>. I changed my static include to a dynamic include. Still no progress.

July 29, 2004 at 5:55 pm #211157 Reply

Riyad Kalla
Member

Rick,
Can you explain in more deatil what the problem in your situation is, and maybe a snippet of the code that is causing problems, what the errors are etc? Also can you please post all the information we request in the [URL=http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-393.html]Posting Guidelines[/URL] thread at the top of this forum? That will give us some context so that we can determine if this is an installation issue, a configuration problem, or a bug. Thanks.
Author

Posts

Viewing 15 posts - 1 through 15 (of 15 total)