Hey Toby > > Deriving a new DocumentFactory allows you to have more fine grained > > control > > over the flyweight policy. For example, the SchemaDocumentFactory (in > > org.dom4j.schema package) implements XML Schema Data Types by associating > > different DocumentFactory implementations with different QName instances > > in > > a schema. > > Pretty cool. I will try out it as I download beta 0.4. As I have to process > a schema file it would be nice chance to see it in action :-). > > You spend a lot of time to improve dom4j. That's honorable. Tell me if I can > help you. > > Happy coding (Not in the sence of COBOL...) Please dive in and help out if you want to! ;-) There's plenty to do. Here's the main to do list:- http://dom4j.org/todo.html Probably top of the list should be the writing of articles, user guides and documentation. If you fancy helping out with some coding, a gentle introduction might be to try write some JUnit test cases that try to break the API ;-). I've tried to write them as I develop but I'm sure there could be many more and the more tests, the more robust the software. If you fancy something a little more heavy duty coding, another area that needs attention is the native DOM implementation of the dom4j API in the org.dom4j.dom package. It compiles but is some way away from full DOM compliance. Thats certainly an area you could dive in and fix if you wish. (There's a DOM compliance test here that it would be great to pass one day soon: http://xmlconf.sourceforge.net/ I'm still in the middle of XML Schema Data Type support right now but when its finished you could investigate adding full XML Schema support (i.e. doing the validation of complex types). Or implementing some other validation engines such as Schematron or TREX. Another area of research is a DTD aware DocumentFactory implementation - maybe knowing about the document structure before parsing begins could result in faster & less memory Element / Attribute / DocumentFactory impleme ntations, or a more clever SAXReader... Other smaller chunks could be an DocumentFactory & Element implementations of the XLink or Xinclude specs. James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ dom4j-dev mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dom4j-dev
