 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | Document properties | Document properties 2004-01-26 - By phil@(protected)
Back
<html><body>
<p><tt>>>>JDOM makes it even simpler than that : Just declare the
namespace mapping <br>
using Element.addNamespaceDeclaration and it will be made available to Jaxen
<br>
when in scope.<<<</tt><br>
<br>
<tt>Well, I think this is not obvious as we cannot rely on document namespaces,
as the alias may be not the same on different documents, while the XPath is
constantly using the same.</tt><br>
<br>
<tt>The idea of adding XPath dedicated namespace entries force to change the
document content, and raise a problem when saving the document. How can we
remove these namespaces safetly, as we may don't what is part of the original
document and what is not. Also, when to remove this?</tt><br>
<br>
<tt>I think we should distinguish the namespaces that defines the document
content itself, and namespaces dedicated to XPath evaluation. Having such a
property at the document level will be an helpful add-on.</tt></body></html>
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@(protected)
.com
Earn $52 per hosting referral at Lunarpages.
|
|
|
