Hi richard et al, > == CVS -> Subversion == +1 from me I use SVN for all our projects and this is one of the last 2 CVS project that I work on
> == Dependencies == Jaxen 1.2 is nearly out I believe > a) should we upgrade all dependencies to current versions > to see if dom4j runs > comfortably in a modern environment ? > - or - This has my vote I think that we should also conconsider any API chnages that the community need to enable the use of dom4j to be improved. For example, A few thinks that I would like to see ... For me I would like to see the DocumentFactory as accessable from a Node (or at least the elements and attributes if the rest is an issue). It is there is you know how to look for it but it is a side effect rather than by intent I would like the DocumentFactory to be an interface I would like Element to include Apis for getElement(int), getElementCount() and a few others Similarly I would like to see mechanisms to allow readonly and copy lists of content to be available efficiently I would like to use events when operations occur on a node (I have a product that provides workflow based on retrofitting this facility into DOM4J) Some of the above are simple and probably dont ruffle too many feathers, but I am sure that some people will want to flame me (please resist). I believe that we should use this oppertunity to fill any holes that the community see need to be filled to simplify use and extension Mike ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ dom4j-dev mailing list dom4j-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dom4j-dev
