XSLTMethod - Add: Create an XSLTMethod

  XSLTMethod is a Zope object that represents an association between
  an XML document and a compatible XSLT transformer.  The XSLTMethod
  automatically runs the XSLT transformation and renders the result
  when called.  It may be called from the web, from DTML, via a Zope
  Page Template, etc.

  XSLTMethod _itself_ contains neither the source of the XML
  document, nor the source of the XSLT transformer. Instead, it points to
  an XSLT transformer and is *applied* to an XML document.
  to one of each.  The XML document is obtained from any Zope object
  that can render ASCII.  For example:

  - Data could be retrieved from a database and returned as a
    well-formed XML document

  - An XML document could be stored as the text of a DTMLDocument,
    Page Template, ParsedXML, File, etc. etc.

  The XSLTMethod is applied to the XML source Zope object in the
  same way that a PythonScript or DTMLMethod might be applied to a Zope
  object.

  By default, the XSLTMethod does not do any caching.  However, if
  caching has been requested, *AND* there is a cache manager
  available, XSLTMethod will cache its results.  When the results of
  the transformation have been cached, they will not be recomputed
  unless the source XML document or the transformer changes.
  
  See the readme and tutorial files for more information.

  Entry Fields

    STANDARD ZOPE SETTINGS

      'ID' -- The standard Zope object identifier.
	This must not be left blank.

      'Title' -- The optional title of the XMLTranform object.
  
      'Description' -- The optional description of the XSLTMethod
  	 object.

    XML SETTINGS

      'XSLT Processor' -- A menu giving the names of the available
         XSLT processors.  Choose the one you want to use for this
         transformer.  It will be used whenever this transformer 
         is applied to a Zope object that yields XML.
         
      'Transformer ID' -- The ID of the XSLT for this XSLTMethod
         to use.  It will be found by acquisition, so it can reside
         in this folder or any parent Zope folders, up to the root
         of the hierarchy.  **IMPORTANT** folder names can also be used,
         if the transformer is located in a sibling folder (rather
         than parent, grandparent, etc.) for example
         'asibling/directory/myxslt' is a valid transformerID.

      'Behave like...' -- What kind of Zope object should the transformer
         produce?  For example, if 'behave_like' is set to DTMLDocument,
         then dtml expressions in the result will be evaluated. This
         property can be changed later.  The most natural setting, though, is
	 probably to behave like the source object.  That is, if you apply
	 a transformer to a DTMLDocument, produce another
         DTMLDocument, and so on.   However, the source object must be one
         of the supported options in that case.
         
      'Cache Manager' -- If a cache manager is
 	 found, this displays a link to it.  If not, it displays
	 the message 'Not available'

      'Caching Behavior' -- Whether or not to cache the results of
         transformations, assuming a cache manager is available.
	 Caching is nearly always a good idea; it provides vastly
         improved performance.  Select 'never cache' for situations
         such as when you are debugging a problem or when the XML
	 source document changes dynamically on a call by call basis
         (for example, when it consists of data that is retrieved from a
         database, etc.).  This property can be changed later.