- This topic has 9 replies, 4 voices, and was last updated 17 years, 3 months ago by
.
-
Posts
-
hi,
i want to migrate my project from netbeans to myEclipse.
in the jsp page i get the following warning – undefined attribute name for the
namespaces that are bolded (pls look at the value of the namespace as well).
<jsp:root version=”1.2″ xmlns:f=”http://java.sun.com/jsf/core” xmlns:h=”http://java.sun.com/jsf/html” xmlns:jsp=”http://java.sun.com/JSP/Page” xmlns:ui=”http://www.sun.com/web/ui”>why is that and how can i fix it?
thanks
i’ve created a web project and tried to import the netbeans project into it.
i used several options, none of which has succeeded.
just to make sure that i do right, how should i do it?btw, it’s a vwp netbeans project, that is different than a regular web project.
thanks.
You cant import the project like this. You will have to create a new project in MyEclipse and then copy and paste parts from your old project.
i know. this is exactly why i turned here for help…
i managed to convert all other things. this is the last thing that
was left for me to do. this is the only thing that separates me
from working with myEclipse.
🙂is there a way to overcome the namespace recognition problem?
Actually, I came across this exact same problem. It is independent of any NetBeans to Eclipse migration. It has to do with MyEclipse not being able to recognize taglibPrefix for XML-like JSP syntax. The actual syntax as per JSP 2.0 spec (haven’t verified with 2.1) is:
<jsp:root xmlns:jsp=”http://java.sun.com/JSP/Page” [xmlns:taglibPrefix=”URI” ]+ …
version=”1.2 | 2.0″>
</jsp:root>Where the taglibPrefix is supposed to be a user-defined custom tag prefix, as is the case with your “f”, “h” and “ui”. Although MyEclipse warns the user about an unrecognized attribute name, once your files are deployed, it works.
It is an annoyance some of us would like to solve. I am hoping someone in this forum can tell us how.
I forgot to mention earlier that I have found this to be a problem only with simple JSP documents. In an HTML based JSP document, you could solve it likewise:
<jsp:root xmlns:jsp=”http://java.sun.com/JSP/Page” version=”1.2″>
<html xmlns:f=”http://java.sun.com/jsf/core” xmlns:h=”http://java.sun.com/jsf/html” xmlns:ui=”http://www.sun.com/web/ui”>
:
:
</html>In fact, you could specify the xmlns:taglibPrefix for any parent element under which you intend to use these custom tags. e.g.
<jsp:root xmlns:jsp=”http://java.sun.com/JSP/Page” version=”1.2″>
<someCustomElement xmlns:f=”http://java.sun.com/jsf/core” xmlns:h=”http://java.sun.com/jsf/html” xmlns:ui=”http://www.sun.com/web/ui”>
:
<f::set var=”aStringVariable” value=”Just a test” />
:
</someCustomElement>Hope you’re able to use this info to temporarily solve this until someone comes up with the “right” way.
arvhville,
Thank you for following up with all that information for the original poster. Unfortunately you are right we are still working through some sticking points with the JSP 2.0 support (JSP Documents) and this is one of the changes we have yet to make.
