cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From volker.schm...@basf-it-services.com
Subject Problems with org.apache.excalibur.xml.xslt.XSLTProcessorImpl
Date Sun, 18 May 2003 11:33:18 GMT
Hi,

I found out a problem using
"org.apache.excalibur.xml.xslt.XSLTProcessorImpl".

If use-store is true the stylesheet template is cached inside the store and
reused for the next transformation. The problem is, that the template and
the factory hold a reference to the URIResolver which is the
XSLTProcessorImpl itself.
Is the URIResolver only used while creating the template? If yes the
current implementation works but we should set the URIResolver to null
after the template is created. If no, we may be use an URIResolver
(XSLTProcessorImpl) which is already recycled and an other problem is that
the resolve method isn't  ThreadSafe. This is an problem because the same
template is used from multible threads.

In Cocoon the template is automatic put into an persistent store if the
memory store is full. The XSLTProcessorImpl is not serializable which ends
in an java.io.NotSerializableException. I think it doesn't make sense to
store an XSLT-Template into an persistent store ?

I also propose to make the Validity check configurable, this will improve
performance in productiv environments.

Volker




Mime
View raw message