I have written a custom Transformer that extends the AbstractDOMTransformer. The transformer needs the entire XML document to do some analysis and then returns another XML doc (which happens to be SVG). The actual transformer completes in 1.5 seconds. I am seeing some timing gaps in the log file that I cannot account for and am not sure what they mean. It seems that the XercesParser is taking up a great deal of time during lookup and decommissioning. Is this because I have to change from a SAX to DOM then back to SAX for Cocoon to serialize? Can anyone shed some light on why the following is taking so much time?
DEBUG (2002-02-08) 14:46.37:153 [cocoon ] web-5/DefaultComponentFactory: ComponentFactory creating new instance of org.apache.cocoon.components.parser.XercesParser. DEBUG (2002-02-08) 14:46.37:153 [cocoon ] web-5/DefaultComponentFactory: no logger attribute available, using standard logger DEBUG (2002-02-08) 14:46.37:153 [cocoon ] web-5/XercesParser: Looking up org.apache.cocoon.components.resolver.Resolver DEBUG (2002-02-08) 14:46.45:765 [cocoon ] web-5/SimilarityMatrixTransformer: SimilarityMatrixTransformer START DEBUG (2002-02-08) 14:46.47:117 [cocoon ] web-5/SimilarityMatrixTransformer: SimilarityMatrixTransformer END DEBUG (2002-02-08) 14:46.52:986 [cocoon ] web-5/DefaultComponentFactory: ComponentFactory decommissioning instance of org.apache.cocoon.components.parser.XercesParser. Maybe this needs to be cached? Thanks, Aaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
