Well, DOMUtils is now dependent on JDOM for getting the string value of a node (at least in the webdavclient). I haven't used JDOM much myself either (prefer dom4j) but the little bit that I've done with it has been easy enough.
-James >>> [EMAIL PROTECTED] 7/27/2004 2:22:22 AM >>> > >>> There is one thing I think MUST be done before the release. I noticed > >>> that currently the org.apache.util package is being maintained at two > >>> separate places in the CVS! Both in src/util and in > >>> webdavclient/clientlib/src/java. Surely this must be consolidated. > >> > >> > >> > >> Hmmmm, I am not quite sure, as server and client really became > >> seperate projects. > >> > > > > But the class definitions look 90% similar to me. Why would you NOT want > > that code consolidated. It just needs to be sorted out and the build > > system needs to be changed a bit. If noone beats me to it I volunteer to > > do it. Probably won't have time before beta1 though. > > I was wondering, this code looks so general isn't it available somewhere > else in Jakarta? Maybe in commons? Yes, that's a good idea. Most of that stuff is available in Commons Codec, which will also be used by Commons Httpclient. Furthermore, I think the client library actually uses only a small subset of the classes left in org.apache.util, so most of that could be eliminated anyway. The most heavily used parts are for sure the XMLPrinter and the DOMUtils. Now that Daniel (was it him?) has introduced a dependency on JDOM, I wonder if we could replace the use of these classes by their JDOM equivalents. However I would like to hear other opinions on this as I have no experience with JDOM myself. Ingo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
