I just wanted to add, that if you use SAX, the value for an information without namespace is the empty string whereas in DOM this is null! Xalan is very tolerant as it can also work - in most cases, but not always! - with a null value using SAX
Carsten > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 22, 2003 2:01 PM > To: [EMAIL PROTECTED] > Subject: [SOLUTION] Upgrade to 2.1.2 - Paginator does not work > correctly! > > > > > The problem was not the upgrade to 2.1.2, but the change to SAXON 6.5.3 > > SAXON requires an empty string as input parameter for the NS. The > paginator > used null. > XALAN 2.5.1 is fine with both. > > eg. > atts.addAttribute(null, "page", "page", "CDATA", > > String.valueOf(pagesheet.getPageForItem(item, > itemGroup))); > > looks now like: > atts.addAttribute("", "page", "page", "CDATA", > > String.valueOf(pagesheet.getPageForItem(item, > itemGroup))); > > > The new source will be comitted by Carsten (thank you!) > > Have a nice day! > > Manfred > > ------------------------------------------------------------------ > -------------------------------------- > Hello * > > I just upgraded one of my webapps from 2.1 to 2.1.2 > Everything works fine except the paginator. > > I get the following exception: > > [10/16/03 15:57:15:234 GMT+02:00] 6c2af952 WebGroup I SRVE0091I: > [Servlet LOG]: ERROR (2003-10-16) 15:57.15:141 [root ] > (/rzbcan/cansearch_serial_letter(1)) > Servlet.Engine.Transports:9/CocoonServlet: Internal Cocoon Problem > org.apache.cocoon.ProcessingException: Unable to get transformer handler > for stylesheets/html/content_error.xsl: > org.apache.excalibur.xml.xslt.XSLTProcessorException: Exception > in creating > Transform Handler > at > org.apache.cocoon.transformation.TraxTransformer.setup(TraxTransfo > rmer.java:307) > at > org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.s > etupPipeline(AbstractProcessingPipeline.java:394) > at > org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessi > ngPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:652) > at > org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.p > reparePipeline(AbstractProcessingPipeline.java:508) > at > org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.p > rocess(AbstractProcessingPipeline.java:470) > at > org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.i > nvoke(SerializeNode.java:147) > at > org.apache.cocoon.components.treeprocessor.AbstractParentProcessin > gNode.invokeNodes(AbstractParentProcessingNode.java(Compiled > Code)) > > My pipeline works perfectly if the paginator transformer is on the last > position before any serializer. > > But when i use any other (tried even with the log transformer) transformer > after the paginator this exception occurs > Does anybody know how to solve this or where to look after this > dependency? > > kind regards > Manfred > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
