4
By all means help yourself to any of these tasks if you fancy
5
rolling your sleeves up and doing some development, tuning, testing or
6
documentation. Any contributions will be greatly received.
13
* As suggested by Robert Lebowitz, consider the pretty printing
14
and OutputFormat to allow very large text nodes to wrap their
15
text at (say) 80 characters per line.
17
* Implement a Saxon adapter so that the SAxon XSLT engine can work
18
natively on top of dom4j.
20
* implement a Locator Element that maintains the column & line number that
21
errors may occur on for better debugging.
23
* implement a proper lazy tree parsing mechanism using the XPP pull parser.
25
* JDBC ResultSet implementation of an Element so that XPath and XSLT can be
26
easily done on a JDBC result set.
28
* Integrate Dennis Sosnoski's XML-Stream work for the default serialization
31
* Support XPath and XSLT patterns in the ElementHandler mechansim
33
* As suggested by Kesav Kumar Kolla, implement a better, mutable Swing TreeModel
34
possibly along with an optional document event mechansim
36
* get the DOM implementation to pass the DOM conformance tests at
37
http://xmlconf.sourceforge.net/
39
* a persistent dom4j implementation using XMLDB or some other persistence
42
* investigate the generation of more optimal Element implementations based on
43
a schema definition, which could still take additional extra schema adjuncts if necessary
44
but would by default use instance member variables for attributes. e.g.
45
<customer id="123" name="James" location="UK"/>
49
public class CustomerElement extends DefaultElement {
52
private String location;
56
So the performance benefit of using a bean would remain yet the XPath, XML, SAX benefits would
57
remain, indeed the use of the 'bean' would be invisible.
59
Though this might well be similar to using the BeanElement.
66
* make cookbook fit for dom4j 1.2
68
* adding UML diagramms into cookbook
70
* add a easier instruction for programmers that starts to use xml and
71
a instruction for programmers that came form jdom world
73
* add the test-suite html output created by junit-report to project page.
75
* improve FOp output for source code samples
80
These features have been developed but require more testing to
81
determine that they are complete...
83
* support for setExpandEntities(true) to expand entities, so that
84
text using "&" could just be treated as a String. So
86
could be treated as a single Element with a Text node containing a String
89
* merging adjacent text nodes; use an internal StringBuffer to add multiple
90
characters() SAX events together.
92
* whilespace removal option.
93
Without access to a schema or DTD its hard to do proper whitespace
94
removal thanks to mixed content, however a simple option for
95
data-related XML applications, to ignoring all whieespace-only nodes
101
would only contain 1 child <name> element and not 2 whilespace nodes.
103
* support of XMLDB native database (org.dom4j.persistence)