Re: cvs commit: cocoon-2.0/lib/core xalan-2.5.1.jar xercesImpl-2.4.0.jarxml-apis.jar xalan-2.3.1.jar xercesImpl-2.0.0.jar

2003-06-09 Thread Steven Noels
On 6/06/2003 20:50 Joerg Heinicke wrote: Carsten Ziegeler wrote: But there is another reason for this mail: Now with the current XSLTC we can switch to it as default processor in 2.0 too, can't we? I'm currently -1 on this because imho xsltc has not proven to be 100% working and I think we

Re: cvs commit: cocoon-2.0/lib/core xalan-2.5.1.jar xercesImpl-2.4.0.jarxml-apis.jar xalan-2.3.1.jar xercesImpl-2.0.0.jar

2003-06-06 Thread Sylvain Wallez
Joerg Heinicke wrote: Though we will get again endorsed lib problem questions on the users list, I updated the XML lib jars to their latest releases as in Cocoon 2.1. I hope nobody has something against this. At least we have a good explanation and solution for these issues now

Re: cvs commit: cocoon-2.0/lib/core xalan-2.5.1.jar xercesImpl-2.4.0.jarxml-apis.jar xalan-2.3.1.jar xercesImpl-2.0.0.jar

2003-06-06 Thread Sylvain Wallez
Sylvain Wallez wrote: Joerg Heinicke wrote: Though we will get again endorsed lib problem questions on the users list, I updated the XML lib jars to their latest releases as in Cocoon 2.1. I hope nobody has something against this. At least we have a good explanation and solution for these

Re: cvs commit: cocoon-2.0/lib/core xalan-2.5.1.jar xercesImpl-2.4.0.jarxml-apis.jar xalan-2.3.1.jar xercesImpl-2.0.0.jar

2003-06-06 Thread Joerg Heinicke
Sylvain Wallez wrote: Actually, ParanoidCocoonServlet can be used to run *any* servlet. So I'll commit the changes in the 2.0 CVS also, so that we can point users to this page. Nice to hear ... But there is another reason for this mail: Now with the current XSLTC we can switch to it as default

Re: cvs commit: cocoon-2.0/lib/core xalan-2.5.1.jar xercesImpl-2.4.0.jarxml-apis.jar xalan-2.3.1.jar xercesImpl-2.0.0.jar

2003-06-06 Thread Joerg Heinicke
Isn't it already the default ? The TreeProcessor has now been around for more than a year... Yep. I checked and the TreeProcessor _is_ the default engine. searched for tree in 2.0 cocoon.xconf and didn't find it. after a closer look I found it. Joerg

Re: cvs commit: cocoon-2.0/lib/core xalan-2.5.1.jar xercesImpl-2.4.0.jarxml-apis.jar xalan-2.3.1.jar xercesImpl-2.0.0.jar

2003-06-06 Thread Sylvain Wallez
Joerg Heinicke wrote: Isn't it already the default ? The TreeProcessor has now been around for more than a year... Yep. I checked and the TreeProcessor _is_ the default engine. searched for tree in 2.0 cocoon.xconf and didn't find it. after a closer look I found it. The TreeProcessor is

Re: cvs commit: cocoon-2.0/lib/core xalan-2.5.1.jar xercesImpl-2.4.0.jarxml-apis.jar xalan-2.3.1.jar xercesImpl-2.0.0.jar

2003-06-06 Thread Joerg Heinicke
Carsten Ziegeler wrote: But there is another reason for this mail: Now with the current XSLTC we can switch to it as default processor in 2.0 too, can't we? I'm currently -1 on this because imho xsltc has not proven to be 100% working and I think we should at least in 2.0.x have a fully working

Re: cvs commit: cocoon-2.0/lib/core xalan-2.5.1.jar xercesImpl-2.4.0.jarxml-apis.jar xalan-2.3.1.jar xercesImpl-2.0.0.jar

2003-06-05 Thread Joerg Heinicke
Though we will get again endorsed lib problem questions on the users list, I updated the XML lib jars to their latest releases as in Cocoon 2.1. I hope nobody has something against this. At least we have a good explanation and solution for these issues now

Re: cvs commit: cocoon-2.0/lib/core xalan-2.5.1.jar xercesImpl-2.4.0.jarxml-apis.jar xalan-2.3.1.jar xercesImpl-2.0.0.jar

2003-06-05 Thread Vadim Gritsenko
Joerg Heinicke wrote: Though we will get again endorsed lib problem questions on the users list, I updated the XML lib jars to their latest releases as in Cocoon 2.1. I hope nobody has something against this. At least we have a good explanation and solution for these issues now