[Zope-xml] XMLTransform permanently binding to XSLT processor?

[Craeg K Strong]

Hello:

Ah yes.  This capability is listed on the TODO list:

   Ability to switch XSLT Processors on the fly -- Some sort of "self
     upgrading mechanism so one can switch to a different processor
     at run time.  May be related to ZSyncer issue above

It sounds like this should be a higher priority (it is currently
pretty far down on the list..)?   I might be able
to make it part of the 0.9 release...

BTW, I just heard from Daniel and he indicates that a new libxslt
with "greatly expanded and improved" Python APIs will be released in
3-4 weeks.

I will probably go ahead and make a 0.9 release a week or two after that
to take advantage of all the new features....

--Craeg

Jean Jordaan wrote:
> Hi there
> 
> If I change the XSLTProcessor from 4Suite to libxslt and restart
> Zope, the XMLTransform instance I was busy with doesn't notice the
> change. From the log:
> 
> =======================================================================
> jean at blommie 2-5-1 $ ./start
> ==> var/stupid.log <==
> ------
> 2002-09-16T13:39:05 INFO(0) zdaemon zdaemon: Mon Sep 16 15:39:05 2002: 
> Houston, we have forked
> [...]
> ------
> 2002-09-16T13:39:08 INFO(0) XMLTransform: Imported XSLTProcessor: 
> Products.XMLTransform.LibXsltProcessor.LibXsltProcessor
> [...]
> ------
> 2002-09-16T13:39:22 INFO(0) XMLTransform styleSrc: 
> <Products.XMLTransform.FourSuite12Processor.ResolvingInputSource 
> instance at 0x97d4cec> systemID: 
> http://blommie:15080/xml/registry/simple.xsl
> =======================================================================
> 
> How can the styleSrc be a FourSuite12Processor.ResolvingInputSource
> instance if LibXsltProcessor was imported? There is no XML Transform
> Cache Manager.
> 
> If I delete and recreate the XMLTransform, the new one uses
> LibXsltProcessor.