Re: XalanNamespacesStack::PrefixResolverProxy persistence

2006-09-13 Thread David Bertoni
Paul Lalonde wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I will read the source in the future. Point taken :-) I'm just using it as a simple container right now, so this should be ok for now, but I know it doesn't solve my problem in the general case. I have a bunch of XML document

Re: XalanNamespacesStack::PrefixResolverProxy persistence

2006-09-13 Thread Paul Lalonde
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I will read the source in the future. Point taken :-) I'm just using it as a simple container right now, so this should be ok for now, but I know it doesn't solve my problem in the general case. I have a bunch of XML documents that I have to ext

Re: XalanNamespacesStack::PrefixResolverProxy persistence

2006-09-13 Thread David Bertoni
Paul Lalonde wrote: Do I have to build a new XalanNamespacesStack::PrefixResolverProxy every time the NamespacesStack changes, or does it remain synchronized? If you look at the source code, you'll see that PrefixResolverProxy only calls into the XalanNamespacesStack instance, so there's no ne