you are parsing the xml correctly, the trouble is that you are not
displaying it correctly.
From your code:
x:out select=$parsedxml//*/
This will show nothing, as the String XPath value of your whole xml is
empty
c:out value=${parsedxml}/
This shows [#document: null], since you'r displaying an
No problem, it just means you can't take advantage of some of the Servlet
2.4/JSP 2.0 features. Actually, this looks like a problem with page validation
as opposed to normal JSP vs. JSP document. Can you post the part of the page
that's generating the error (including any taglib directives it
I've seen two different ways to declare taglibs in jsp files:
%@ taglib prefix=fmt uri=http://java.sun.com/jsp/jstl/fmt; %
%@ taglib prefix=html uri=/WEB-INF/lib/struts-html-el.tld %
What is the difference between referencing http://blah http://blah/ blah
and /WEB-INF/blah blah? Are they
The question is not which is proper, Brian. I think that both these ways
of doing this just confuse new people and are very bad ideas. What I do is
this:
%@ taglib uri='struts-bean'prefix='bean' %
This should make it clear that the uri is not a uri at all. Most
supposed url and
Thanks for your help Kris. With some reading, and some input from others, I
think I have it working now.
Had to make sure uri taglib declarations in jsp pages matched those in
web.xml. I also learned that the uri is really just a unique name, as the
acronym suggests. It doesn't have to point
I'm having a lot of problems connecting to a database using the SQL
tag-lib. I'm using Tomcat 5.0 on Windows. Here is the web.xml source:
?xml version=1.0 encoding=ISO-8859-1?
!DOCTYPE web-app
PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
