> > I had problems with Xalan-J 1.x and newer versions of Xerces as > > well. The solving workaround was to switch to Xalan-J 2.1.0 which > > works fine with Xerces-J 1.4.1 > > Unfortunately I've wrote an API based an C++ version of Xerces and > Xalan [...] Isn't this a good reason to split the development list into xalan-j- dev and xalan-c-dev? (if i'm alone with this opinion please ignore this mail, thx) Regards. -- Bjoern Martin [EMAIL PROTECTED]
- XalanTransformer problem Ciprian Ungureanu
- Re: XalanTransformer problem Bjoern Martin
- Re: XalanTransformer problem Ciprian Ungureanu
- Re: XalanTransformer problem Bjoern Martin
- Re: XalanTransformer problem Ciprian Ungureanu
- Re: XalanTransformer problem David_N_Bertoni
- Re: XalanTransformer problem Ciprian Ungureanu
- Re: XalanTransformer problem Ciprian Ungureanu
- Re: XalanTransformer problem David_N_Bertoni
- Re: XalanTransformer problem David_N_Bertoni
- RE: XalanTransformer problem Peter Murphy
- RE: XalanTransformer problem David_N_Bertoni
