Hi Jesper, Welcome here first!
As you said, one day if PsychoPath supplies a decent API which can satisfy the requirement of both Xalan and Xerces, it will be very easy for Xalan to consume PsychoPath. But as you know, Xalan is known as a XSLT engine, support XSLT 2.0 is very important,necessary and urgent for it. Before the days PsychoPath supplies a easy-to-use API for Xalan, i think implement XSLT 2.0 support for Xalan by merging PsychoPath first, and then add some other features is not a bad choice, for Xalan, just do it is not a bad thing. Once you guys offer a decent API for Xalan, we can change our codes to fit new PsychoPath API. You pointed out some limitations about the merging job, they are really problems. My project aims to implement XSLT 2.0 for Xalan, merging PsychoPath will speed up this project, but i do not extravagant claim that PsychoPath can do everything for Xalan. So, i think,nowadays,merging PsychoPath may be the fastest and best way for Xalan to support XSLT 2.0, if i want to do this job well, i guess help from you guys will be very necessary. your opinion? Xunlong Gui > > > Other than that, I would think that merging the two projects is not > required at all, Xalan-J should be able to simply consume PsychoPath once we > have a decent API which can satisfy the requirements of both Xalan and > Xerces. If not, I thing it would signify a design fault in our API. > > Let's discuss (I've joined this mailing list for this reason)! > > -Jesper >
