- This topic has 6 replies, 3 voices, and was last updated 20 years, 5 months ago by
.
-
Posts
-
I wasn’t sure weather to put this in the feature requests or bugs. This bug is best demonstrated with an example:
I have main.jsp that includes header.jsp and body.jsp. body.jsp uses variables and import statements from header.jsp, which is fine since they are both statically included in main.jsp. However, my page is full of errors since myeclipse doesn’t understand this simple heirarchy. Also, code complete doesn’t work. This makes development with complex jsp pages difficult and messy.
Different issue:
Also, when you click the deploy button, there is no project selected by default. I have posted on this before and thought I was told it was fixed in this latest release (which it isn’t). This seems like a small thing but when servlets don’t hot deploy in an exploded deployment, I end up clicking this button many times when modifying servlets. I’m using Mac OS X 10.3 & 1.4.2 JVM.Thanks,
John Myers
However, my page is full of errors since myeclipse doesn’t understand this simple heirarchy. Also, code complete doesn’t work.
I was able to duplicate this, I’ll send it to the devs and see what their response is.
Also, when you click the deploy button, there is no project selected by default. I have posted on this before and thought I was told it was fixed in this latest release (which it isn’t).
I told you it was fix in your previous thread, and then my next post was a clarification that it had not been fixed in the Beta 1 release.
This seems like a small thing but when servlets don’t hot deploy in an exploded deployment
We will be happy to help you with this issue if you need it to work, but we would need more info about your app server and its setup.
Also please tell us what version of ME you are using.
I have main.jsp that includes header.jsp and body.jsp
The problem is most likely the naming of the files. If header.jsp and body.jsp are not fully compliant and valid JSP pages as standalone pages, they should use the .jspf (jsp fragment) suffix that is mentioned in the spec. For example I have the following code for my ‘main’ jsp:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <%@ page import="com.tomcattest.Junk" %> <%@ page language="java" import="java.lang.*,java.util.*" %> <% String path = request.getContextPath(); String basePath = "http://"+request.getServerName()+":"+request.getServerPort()+path+"/"; %> <HTML> <HEAD> <BASE HREF="<%=basePath%>"> <TITLE>My JSP 'OrionJSP2.jsp' starting page</TITLE> <META HTTP-EQUIV="pragma" CONTENT="no-cache"> <META HTTP-EQUIV="cache-control" CONTENT="no-cache"> <META HTTP-EQUIV="expires" CONTENT="0"> <META HTTP-EQUIV="keywords" CONTENT="keyword1,keyword2,keyword3"> <META HTTP-EQUIV="description" CONTENT="This is my page"> <!-- <LINK REL="stylesheet" TYPE="text/css" HREF="styles.css"> --> </HEAD> <BODY> <%@ include file="./deepother/TomcatInclude3.jspf" %> This is the WebLogicJSP3.jsp page. <BR> <% out.println("\nJava output: " + date); %> </BODY> </HTML>and the following is the complete content of the jspf file:
<% Date date = new Date(); out.println("Include's date is " + date); Junk junk = new Junk(); int ret = junk.getValue(); %>Notice that the import for Junk is in the main JSP file and there is no problem with the fragment and also that the reference to ‘date’ is in the main jsp file although declared in the fragment. Again, no problems.
Different issue:
Also, when you click the deploy button, there is no project selected by default.Actually, that’s not correct. Any project that is selected in the Package Explorer will be selected as the default. However, if there is no workbench selection, the previous selection is currently not remembered.
I have posted on this before and thought I was told it was fixed in this latest release (which it isn’t).
You were most likely told that it would be addressed in 2.8/3.8. However, beta 1 is not near feature complete yet so there is still some time. 🙂
jmmyers@sark.com,
Scott correctly pointed out that your header and body pages should actually be JSP fragment (or segment) ending with a “jspf” extension as they are not standalone-compilable JSPs.Upon changing the name and cleaning the application using the jspf extension did work. Thanks for the tip.
Also, I was not getting a default option in the deploy window because i did not have a project selected. There is only one project though, and it seems odd I should have to select the one project. The default is to select NO project. This may be a Mac OS X thing, not sure if it happens on other platforms.
Using 3.8 beta 1
