- This topic has 6 replies, 3 voices, and was last updated 20 years, 6 months ago by
.
-
Posts
-
The only JSP 2.0 feature listed in 2.8/3.8 is the JSP 2.0 preview. I realize that we all use the tool differently, but I can preview in my browser!
With the JSP 2.0 web.xml schema in use, taglib context-completion is completely broken. Furthermore, all my JSP’s show up as problematic (red X decoration) because the referenced taglib is no longer looked up in web.xml under web-app/taglib but rather web-app/jsp-config/taglib. For me this is huge.
Is this going to be fixed? I may be somewhat bitter becuase myEclipse kept validating my 1.2-formatted web.xml as “OK” even though the 2.0 schema (not the old DTD) was referenced.
If I’m missing something then please point me in the right direction. If this is meant to be working, and I’ve found a bug, I’ll be happy to re-post in the bug forum and provide details.
Thanks,
Chris
Chris,
The only JSP 2.0 feature listed in 2.8/3.8 is the JSP 2.0 preview. I realize that we all use the tool differently, but I can preview in my browser!
I believe we have a communication problem here. What the feature list is referring to is a ‘preview’ (meaning not full production capability) of some JSP 2.0 features in 2.8/3.8. It has nothing to do with previewing JSP pages as that is already handled in the preview pane of the JSP editor in the 2.7 release.
With the JSP 2.0 web.xml schema in use, taglib context-completion is completely broken.
That is because we don’t support JSP 2.0 in MyEclipse yet. If you want to use JSP 2.0 syntax, then you should disable JSP validation on the JSP editor’s preference page so it won’t report the problems you’re seeing.
Furthermore, all my JSP’s show up as problematic (red X decoration) because the referenced taglib is no longer looked up in web.xml under web-app/taglib but rather web-app/jsp-config/taglib. For me this is huge.
That sounds more like a configuration problem, if I understand you correctly. It’s the taglib directive in web.xml that tells the editor where to look for taglibs.
I may be somewhat bitter becuase myEclipse kept validating my 1.2-formatted web.xml as “OK” even though the 2.0 schema (not the old DTD) was referenced.
You’re confusing ‘validating as ok’ with ignoring and not validating at all. Since your web.xml referenced a 2.0 schema, and we don’t support JSP 2.0 schema validation, no validation was performed. Validation can only be performed against the JSP 1.2 DTD.
Hope that clears things up a little. Sorry for confusion.
I believe we have a communication problem here. What the feature list is referring to is a ‘preview’ (meaning not full production capability) of some JSP 2.0 features in 2.8/3.8.
Yep that was my mistake, sorry about that. I’m looking forward to seeing the new features!
That is because we don’t support JSP 2.0 in MyEclipse yet.
Understood. I’ll pray to the MEIDE dietys to include this in x.8 🙂
That sounds more like a configuration problem, if I understand you correctly. It’s the taglib directive in web.xml that tells the editor where to look for taglibs.
Probably is, and due to the above lack of JSP 2.0 support. I’ll wait for x.8.
You’re confusing ‘validating as ok’ with ignoring and not validating at all. Since your web.xml referenced a 2.0 schema, and we don’t support JSP 2.0 schema validation, no validation was performed. Validation can only be performed against the JSP 1.2 DTD.
This I don’t understand. I see that x.7 does not support JSP 2.0. However, my web.xml is simply an XML document with a referenced schema. The MEIDE XML editor supports validation against a schema, does it not? Should it care that it happens to be the JSP 2.0 deployment descriptor schema?
The validation command is available and clearly performs *some* task when activated, but does not report any errors. This leads the user to believe that the XML was well-formed AND valid. If such a feature doesn’t function in the context, or doesn’t function at all, it should be greyed out or come with a one-time notification that it is a work in progress (or in the Preferences like the Eclipse SDK does).
-Chris
The MEIDE XML editor supports validation against a schema, does it not?
Nope, it doesn’t.
If such a feature doesn’t function in the context, or doesn’t function at all, it should be greyed out or come with a one-time notification that it is a work in progress (or in the Preferences like the Eclipse SDK does).
You are absolutely right, I will file a request for this enhancement. Thank you for the feedback, it is clear that we overlooked good user feedback in this case. Especially since something ‘does happen’ when you try and validate an XML file referencing a schema.
We’ll remove the validate option from the menu for XML files that reference schemas to avoid this confusion beginning with the first beta of 2.8. We’ll then add it back in only when available. Sorry for the confusion.
