<html><body>
<p>Hi guys,<br>
<br>
I'm wondering if we can natively carry a map of properties into a JDOM Document (ie: without creating a custom Document class, as documents may be created by third party code). This capability currently exists in some DOM implementation.<br>
<br>
One use case is with XPath & Namespace. Currently, when using Jaxen, we have to pass it a context containing the mapping between aliases and URI. And this can be cumbersome, if you have lot of code located into different places. Microsoft solved this pb in InfoPath quite elegantly and efficiently, by allowing user to set a Document property containing the namespace mapping.<br>
Ex:<br>
<font color="#008000" face="Courier New"> // The following line is created by Microsoft Office InfoPath to define the</font><br>
<font color="#008000" face="Courier New"> // prefixes for all the known namespaces in the main XML data file.</font><br>
<font color="#008000" face="Courier New"> // Any modification to the form files made outside of InfoPath</font><br>
<font color="#008000" face="Courier New"> // will not be autmatically updated.</font><br>
<font color="#008000" face="Courier New"> //<namespacesDefinition></font><br>
<font face="Courier New"> XDocument.DOM.setProperty("SelectionNamespaces", 'xmlns:my="http://schemas.microsoft.com/office/infopath/2003/myXSD");</font><br>
<font color="#008000" face="Courier New"> //</namespacesDefinition></font><br>
<br>
And their XPath engine automatically uses this property if available, letting a user write an XPath using 'my:' prefix, without worrying on the mapping, set once for all queries.<br>
<br>
We want to implement such a facility in our framework, but are not able currently to set a custom property to a Document. Don't you think adding a HashMap (left null if not used) is possible? It can have many other use cases...<br>
<br>
Thanks,<br>
<br>
Phil.</body></html>