<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Recursive file listings in XSL-transformations in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/recursive-file-listings-in-xsl-transformations/m-p/239450#M192580</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;By default, Alfresco WCM offers alf&lt;img id="smileytongue" class="emoticon emoticon-smileytongue" src="https://connect.hyland.com/i/smilies/16x16_smiley-tongue.png" alt="Smiley Tongue" title="Smiley Tongue" /&gt;arseXMLDocuments(formName, avmPath) function to be used within XSL-transformations. Apparently parseXMLDocuments function is a method of class org.alfresco.web.forms.FormDataFunctions. Is there an elegant way of extending this class to make it recursive, and enabling it to be used in XSL-transformations (without modifying the class directly)?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What I'd like to do is that every time a WCM-object is created/modified Alfresco would create an index-file containing all the elements of that type by using an XSL template. But we are planning an approach where WCM-objects are not necessarily in the same directory.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Another solution would be to execute a webscript from the XSL (which would recursive go through all the files). But is it possible to call a webscript from XSL. With XSD this is possible, but when I tried the same method in XSL (&amp;lt;xsl:value-of select="webscript://project/load-content-recursively/get?storeid={storeid}&amp;amp;amp;ticket={ticket}&amp;amp;amp;form=wcmType" /&amp;gt;), I get the following Exception:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;javax.xml.transform.TransformerException: org.apache.xpath.domapi.XPathStylesheetDOM3Exception: Prefix must resolve to a namespace: webscript&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;SPAN&gt;Any tips/suggestions? Thanks!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- Pyppe&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Oct 2009 11:46:23 GMT</pubDate>
    <dc:creator>pyppe</dc:creator>
    <dc:date>2009-10-02T11:46:23Z</dc:date>
    <item>
      <title>Recursive file listings in XSL-transformations</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/recursive-file-listings-in-xsl-transformations/m-p/239450#M192580</link>
      <description>Hi.By default, Alfresco WCM offers alf&lt;IMG id="smileytongue" class="emoticon emoticon-smileytongue" src="https://migration33.stage.lithium.com/i/smilies/16x16_smiley-tongue.png" alt="Smiley Tongue" title="Smiley Tongue" /&gt;arseXMLDocuments(formName, avmPath) function to be used within XSL-transformations. Apparently parseXMLDocuments function is a method of class org.alfresco.web.forms.FormDataFunctions. Is there an elegant way of extending this class to make it recursive, and e</description>
      <pubDate>Fri, 02 Oct 2009 11:46:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/recursive-file-listings-in-xsl-transformations/m-p/239450#M192580</guid>
      <dc:creator>pyppe</dc:creator>
      <dc:date>2009-10-02T11:46:23Z</dc:date>
    </item>
    <item>
      <title>Re: Recursive file listings in XSL-transformations</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/recursive-file-listings-in-xsl-transformations/m-p/239451#M192581</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The bit in the XSLT select clause is XPath, which expects axis::node-path[predicate]. The URL you've given has an unknown protocol "webscript", which I think XPath is trying to interpret as a namespace qualifier such as in webscript:thisElement. I think that's why it's confused.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My two cents worth.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Oct 2009 12:53:04 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/recursive-file-listings-in-xsl-transformations/m-p/239451#M192581</guid>
      <dc:creator>rogerp</dc:creator>
      <dc:date>2009-10-02T12:53:04Z</dc:date>
    </item>
  </channel>
</rss>

