Dane, > The functionality mentioned is something Silvain can build as his own layer > above dom4j. Its not that hard to implement. Off the top of my head; for
You are probably right saying that "I can build it on top of DOM4J", but it wouldn't surprise me if others needed the same functionality, so adding it to DOM4J would benifit everybody. Can you tell me why you wouldn't want this to be part of DOM4J? Does it cause problems with existing functionality, or are there conceptual problems? If so, then I must agree with you, but otherwise I think it's not such a bad idea. Silvain _______________________________________________ dom4j-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-user
