Re: Getting rid of xalan and xerces :-)

[EMAIL PROTECTED] wrote: Santiago, I think it is better if you just update the EcsStylesheetElement properly, I don't think using SimpleTransform in ECSStylesheet element or somewhere else as a wrapper for the standard XML API is necessary. I think it is ok to call the standard XML

Re: Getting rid of xalan and xerces :-)

Santiago, I think it is better if you just update the EcsStylesheetElement properly, I don't think using SimpleTransform in ECSStylesheet element or somewhere else as a wrapper for the standard XML API is necessary. I think it is ok to call the standard XML API from the EcsStylesheetElement

Re: Getting rid of xalan and xerces :-)

Santiago, the EcsStyleSheet element works similarly to the EcsServletElement. The purpose of these classes is to allow for deferring exectution of a servlet/JSP or a stylesheet respectively until the ECS tree is traversed, so that the JSP or stylesheet processor can write directly to the

Re: Getting rid of xalan and xerces :-)

[EMAIL PROTECTED] wrote: Santiago, the EcsStyleSheet element works similarly to the EcsServletElement. The purpose of these classes is to allow for deferring exectution of a servlet/JSP or a stylesheet respectively until the ECS tree is traversed, so that the JSP or stylesheet

Getting rid of xalan and xerces :-)

What I really mean is that we found a problem while I was visiting Juan Carlos in Ciudad Real (related with how SAX1 implementations handle namespaces) that made it mandatory for us to try to go into SAX2 --- Xalan2. I did some experiments and I found that migrating Jetspeed to use only