On 6/19/06, Dezbah Duchicela <[EMAIL PROTECTED]> wrote:
Thanks solprovider! I was actually wanting the pure xml file, because the purpose of lenya was to have users graphical make the xml files and then we would take those and export them to an ftp and I would create my own xsl stylesheet to use to conform to our company standards. Is this at all possible? I wanted the pure xml because I have been trying to create a stylesheet with the index_en.xml files provided in the authoring section of my publication and it is not working because the html tags are messing up the xsl reader.
---
The easiest method is to directly access the XML files. This may cause file-locking issues on some operating systems, and would bypass Lenya. A better method is to add a pipeline to access the XML through HTTP. (I did not test any of the following.) == Lenya 1.2 URL: http://server/pub/live/docpath/docid_lang.xml FILE: {pub}/publication-sitemap.xmap ADD: <map:match pattern="**_*.xml"> <map:generate src="content/{1}/index_{2}.xml"/> <map:serialize type="xml"/> </map:match> You could add the functionality as a Usecase rather than add it to the main pipeline. (See the link at the end.) And you might handle URLs that do not specify the language. == Lenya 1.3 URL: http://server/pub/getxml/live/docpath/docid FILE: modules/getxml/module.xmap <?xml version="1.0" encoding="UTF-8"?> <map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0";> <map:pipelines> <map:pipeline> <map:match pattern="{module:module}/**.*"><!-- Remove extension --> <map:generate src="content:://{1}"/> <map:serialize type="xml"/> </map:match> <map:match pattern="{module:module}/**"><!-- No extension --> <map:generate src="content:://{1}"/> <map:serialize type="xml"/> </map:match> </map:pipeline> </map:pipelines> </map:sitemap> content:: (double colon) guarantees the result is XML, so it returns the META information for type="file", such as graphics. Lenya1.3 uses the default language if the language is not specified in the URL. == Lenya 1.4 Ask somebody else. == Using a Lenya1.2 Usecase or Lenya1.3 Module allows you to apply different XSLT to the content. For 1.2, you might read: http://solprovider.com/lenya/multiple solprovider P.S. I thought IBM used Domino for all its CMS needs. Domino does much more than Lenya. What are you doing here? I do not want to discourage you, but my last contract was a Domino infrastructure project for IBM. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
