[EMAIL PROTECTED] wrote: > One is to try to preserve the backward compatability by making NodeSet > implement NodeList, and changing its "native" DTM API to avoid the > conflicts. If we're going to do that, we should do so SOON, since it'll be > a lot harder to justify altering DTM after the next non-developer release. > > The other is to preserve DTM architecture by saying that this cast was > never officially supported in the first place, and require that dbxml -- > like the extensions -- be updated to track Xalan. We could provide them > with a NodeSet.itemAsNode() convenience function, and/or > NodeSet.getNodeList(), either of which would create proxy objects (again, > as we do for extensions)... but dbxml would have to bite the bullet and cut > over.
Hi Joe, There's only one spot in the dbXML source code that uses the NodeLists returned by Xalan, and that's in the XPathQueryResolver. It will be fairly easy to get this code in sync with the latest version of Xalan. I think the problem that we're facing in general is that we link against an older (non-DTM) version of Xalan. This in itself isn't a bad thing, but the GUMP mentality is to make sure that the latest and greatest of any project builds against the latest and greatest of everything else. I think the decision that's made should be made to accommodate developer flexibility, but not at the cost of performance. We don't need a mutable nodelist to be returned, but I can't speak for other developers. --Tom
