Thanks for the reply.
I did not know XQuilla before. I´ll check it out...
What about a Xerces related XSLT processing toolkit? 
Are there some good supported alternatives too?


-----Ursprüngliche Nachricht-----
Von: Ben Griffin [mailto:[email protected]] 
Gesendet: Mittwoch, 6. Mai 2009 14:19
An: [email protected]
Betreff: Re: Project support / maintenance / timeline

Peter,

As a mere user of xercesc/xalanc, albeit within a long-lasting  
commercial project, I was faced with the same dilemma.
In the end, we decided to opt for XercesC/XQilla for it's xquery /  
xpath support, because it appears to be far more active than Xalan-C.

I found the integration of XQilla far more transparent and straight- 
forward than I did managing xalan.
I still believe that XercesC is a really great library, and I hope  
that it will have a long future.

The entire experience of having to wait for a long time to get updates  
to key libraries has been a pretty shaky one.

Best regards
        Ben.

On 6 May 2009, at 12:57, Peter Reiter wrote:

> Hello,
>
> I do have to decide if to use Xalan-C together with Xerces-C in a  
> university research software project. Until now I was not facing any  
> problems using Xerces. However as far as I can see, the Xalan  
> project website seems to be pretty outdated compared to Xerces an  
> compared to the Xalan SVN trunk too.
> For me the current Xalan SVN trunk does not build using Xerces-C  
> 3.0.1 and Visual Studio 8 without errors.
> Nothing that could not be fixed but this leads to my question.
>
> Is the xalan-c project still supported?
> How recommendable is it to start using Xalan-C in a software project  
> that uses Xerces?
> I was not able to find a timeline. What are the future plans for the  
> project?
>
> Thanks.
> Greetings, Peter
>
>
> Dipl.-Ing. Peter Reiter
> Softwareentwicklung
>
> Universität des Saarlandes
> Lehrstuhl für Theoretische Elektrotechnik
> Zimmer 11.03, Gebäude C6.3
> Postfach 15 11 50
> D-66041 Saarbrücken
>
> Tel.: +49 681 302 57495
> Fax: +49 681 302 3157
>
> E-Mail: [email protected]
>
>

Reply via email to