- This topic has 22 replies, 5 voices, and was last updated 18 years, 10 months ago by
.
-
Posts
-
After installing 5.0M2, there is one weird thing:
<%@ include file=”/my.jspf” %>
JSP validator marks this line with a red x and complain:
Syntax error: insert “Finally” to complete TryStatment
This only happend to *.jspf. if I rename to my.jsp and the error disapear.
my platform is: linux, sun-jdk5, eclipse 3.2, MyEclipse 5.0M2
If you navigate to your Window > Prefs > MyEclipse > Editors > JSP settings, do you have jspf extension set for fragments? Also is there anything in the fragment that has a try-catch block in it?
I had reproduce this bug:
first I have a myTaglibs.jsp file which contains:
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%> ... <%@ taglib uri="http://acegisecurity.sf.net/authz" prefix="authz" %>and MyMain.jsp is:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <%@ include file="/include/myTaglibs.jsp"%> <html> <head><title>Main</title></head> <body> <%@ include file="/menu.jspf" %> <!-- blah blah .... --> </body> </html>MyEclipse will complain include /menu.jspf — “Syntax error: insert “Finally” to complete TryStatment”
But if I remove acegi taglib — <%@ taglib uri=”http://acegisecurity.sf.net/authz” prefix=”authz” %>
from myTaglibs.jsp, the complain is disapeared !!I tried struts, jstl, displaytag’s taglib but only acegi causes error.
Can’t image why…
I just downloaded ACEGI and installed it and your URI is wrong, it should be:
http://acegisecurity.org/authzAtleast with the version I got. Can you expand your acegi-security-1.0.1.jar and go into your META-INF and open the TLD, look about 5 lines down for the <uri> tags.
We still use acegi 0.9 now, and plan to upgrade when spring 2.0 ready
anyway, I tried new uri, some of errors are disppeared but some not.
but if I change suffix “.jspf” to “.jsp”, then all validation passed.
If you are able to export this project to a zip and send it to us, we can have a look: support@genuitec.com ATTN Riyad, with a link to this thread so I know why I’m getting it.
The problem has nothing to do with Acegi. I don’t use Acegi, but I get the same error when including the second of several .jspf files. The included file itself is not marked as having errors, but all files including it are.
There definitely is no try-catch block anywhere in my jsp or jspf files, as I never use Java code inside those, so the error message is completely astray.
In the version I used previously, there was at least an option to remove error markers that were errors themselves. Has this been abandoned?
@support-rkalla wrote:
If you navigate to your Window > Prefs > MyEclipse > Editors > JSP settings, do you have jspf extension set for fragments? Also is there anything in the fragment that has a try-catch block in it?
I don’t seem to find this option anywhere. Am I missing something? (I confirm I am using E3.2 with MyE 5.0M2).
./alex
—
.w( the_mindstorm )p.And just another thing…. my code is not about jspf:
<%@ include file="/includes/vendorcontentlist.jsp" %>./alex
—
.w( the_mindstorm )p.Guys,
The more test projects I get to the address above the better, but please include a link to this thread. The issue is that the validator changed quite a bit (for the better) and my guess is that these errors are completely erroneous. The thing is, I need a project that produces the problem so I can send it to the dev team and they can figure out what the *real* problem is.Riyad, for the moment I cannot submit any code as I haven’t got time to trim it down, and my project is the whole code behind InfoQ.com ;-). I hope to get some time next week and look into this. The problem is completely annoying, as I hate having red marks on my projects (frankly speaking I hate the yellow in warnings too 🙂 ).
./alex
—
.w( the_mindstorm )p.Hi!
First of all congrats for getting out the 5.0 final. Unfortunately, I have to report that this is still a bug with the final release, and this means that the whole JSP validation part is a completely missing feature for me. Don’t know what else to say, because this one one of the features I was always relying on, and now that it is missing it is really reducing the benefits I get from MyEclipse.
Some details:
*** Date: Mon Aug 07 21:21:19 EEST 2006 *** Platform Details: <SNIP, please use MyEclipse > About MyEclipse > Installation Summary in the future>I am not completely sure yet, but I think that this scenario happens in my case if the included jsp fragment contains 2 imbricated ww:if tags
(ww tags are tags distributed with WebWork OSS webframework)../alex
—
:Architect of InfoQ.com:
.w( the_mindstorm )p.
