I mean "The reasons always quoted for NOT choosing xalan are"... --- On Tue, 10/11/09, Adam Jenkins <adamjenkinstmpredir...@yahoo.com.au> wrote:
> From: Adam Jenkins <adamjenkinstmpredir...@yahoo.com.au> > Subject: XalanJ future > To: xalan-dev@xml.apache.org > Received: Tuesday, 10 November, 2009, 1:29 PM > Hi Guys, > > A bit off topic here, but I wanted to ask a question about > the future of XalanJ. As a java consultant of many > years, I've always used xalan extensively and like it above > saxon...I've even pushed the extension element and extension > functions framework quite heavily over the years. > Anyway, recently I've noticed a pretty strong trend from > colleagues and clients to use saxon instead. The > reasons always quoted for choosing xalan are: > > 1) No XSLT 2.0 > 2) Slow Performance (relative to Saxon) > 3) Not actively enhanced/developed > > In your opinion, are these valid concerns? I really > don't want to stop using XalanJ, and given I have a fair > knowledge of the underlying code I'd rather have a crack at > solving these concerns before having to change my preferred > xslt translation engine. > > Anyway, any thoughts/opinions would be really really > appreciated. > > Cheers > adam > > > > __________________________________________________________________________________ > Get more done like never before with Yahoo!7 Mail. > Learn more: http://au.overview.mail.yahoo.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org > For additional commands, e-mail: xalan-dev-h...@xml.apache.org > > __________________________________________________________________________________ Win 1 of 4 Sony home entertainment packs thanks to Yahoo!7. Enter now: http://au.docs.yahoo.com/homepageset/ --------------------------------------------------------------------- To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org For additional commands, e-mail: xalan-dev-h...@xml.apache.org
