Hi Warrell and all others,
Thanks for the response,I am trying it without using <xsl:text> but i am unable to generate
<page xmlns:i="http://apache.org/cocoon/include/1.0"> in xml.kindly help me out regarding what should be the corresponding xsl code for getting the bold part as output in xml.
Thanks & Regards,
Arnab Jena
Assistant Systems Engineer
Tata Consultancy Services Limited
Bangalore,Karnataka
India
Mailto: [EMAIL PROTECTED]
Website: http://www.tcs.com
[EMAIL PROTECTED]
03/03/2006 02:58 PM
|
|
Hi Arnab,
I wonder why you are using the aggregate in the generation stage as you are only aggregating from a single pipeline? I'm not familiar with the dasl transformer but there is no reason that I can see why this is not used inline. For debugging purposes I would simplify this aspect and then use cocoon views to have a look at the XML after each stage. Anyway, with respect to the XSL you are using you may not be aware that you don't need to use <xsl:text> to output the <cinclude> tags. Have a look at a Cocoon sample to see a more readable approach :-
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:cinclude="http://apache.org/cocoon/include/1.0">
<xsl:template match="/">
<page>
<title>Supersonic Tour of Apache Cocoon</title>
<content>
<xsl:apply-templates match="toc-section"/>
</content>
</page>
</xsl:template>
<xsl:template match="toc-section">
<h1><xsl:value-of select="@name"/></h1>
<xsl:apply-templates match="toc-item"/>
</xsl:template>
<xsl:template match="toc-item">
<h2><xsl:value-of select="@name"/></h2>
<cinclude:include src=""> </xsl:template>
</xsl:stylesheet>
I'm sure you are aware, when debugging, simplify, simplify, simplify.
Hope this helps. I'm sure the problem is hidden by the unnecessary complexity of the pipeline definition and the XSL.
Regards
Warrell Harries
| IT Services, West Sussex County Council
| Location: Northleigh House Office: +44 (0) 1243-756837 | Email: [EMAIL PROTECTED] |
[EMAIL PROTECTED]
![]() | ![]() [EMAIL PROTECTED] 03/03/2006 06:06 | ![]() To: users@cocoon.apache.org cc: (bcc: Warrell Harries/ICTS/CTG/WSCC) Subject: Re: Generation of xml from xml applying xslt |
Hi all,
I am posting my sitemap samples and xsl for some better reference.
SITEMAP
<map:match pattern="*/index.html">
<map:aggregate element="root" label="source"> //this part generates an xml file based on dasl query/code is given below** <map:part element="documents" src=""
</map:aggregate>
<map:transform src="">
<map:parameter name="previewOrLive" value="{1}"/>
</map:transform>
<map:transform type="cinclude">
<map:parameter name="parallel" value="true"/>
</map:transform>
<map:transform type="i18n">
<map:parameter name="locale" value="en"/>
</map:transform>
<map:transform src="">
<map:serialize type="xml"/>
</map:match>
** <map:generate src="" type="jx">
<map:parameter name="repository" value="{global:repositoryRoot}{global:{1}Path}"/>
</map:generate>
<map:transform type="dasl"/>
XSL
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:dasl="http://cocoon.apache.org/webdav/dasl/1.0"
>
<xsl:output method="xml"/>
<xsl:text><page xmlns:i="http://apache.org/cocoon/include/1.0"></xsl:text>
<xsl:if test="d:displayname = $selectedDocument"> Selected</xsl:if>
</xsl:attribute>-->
<xsl:text><i:include src="" select="@dasl:path"/><xsl:text>"/></xsl:text>
DASL SEARCH IS GENERATING A XML. AFTER APPLYING XSL TO THE GENERATED XML,IT IS FED TO COCOON TRANSFORMER BUT I AM NOT GETTING REQUIRED OUTPUT FROM THE CINCLUDE TRANSFORMER.IT SEEMS AS IF IT IS SKIPPING CINCLUDE TRANSFORMER.
Thanks & Regards,
Arnab Jena
Assistant Systems Engineer
Tata Consultancy Services Limited
Bangalore,Karnataka
India
Mailto: [EMAIL PROTECTED]
Website: http://www.tcs.com
This stuff works 100%
Please post your sitemap, XSL and XML files to the mailing list if you want some help.
Warrell Harries
| IT Services, West Sussex County Council
| Location: Northleigh House Office: +44 (0) 1243-756837 | Email: [EMAIL PROTECTED] |
[EMAIL PROTECTED]
03/02/2006 09:27 PM
|
|
Hi all,
I am working on data retrieval in cocoon but unable to retreive the content.Kindly have a look as i am summarizing my efforts below :
- A generator is producing a xml file.
- This is converted to a format that can be understood by the cinclude transformer by applying an xsl sheet.
- Then after applying the xsl,it is fed to the cinclude transformer in the pipeline.
- But I am not getting the desired output as reqd from the cinclude transformer.It seems as if the pipeline is breaking without executing the cinclude transformer.
- Basically generation of xml from xml applying xsl sheet is not working properly.
If anyone has worked on such stuff,it would nice to have some solutions or suggestions.
Thanks and Regards,
Arnab Jena
Assistant Systems Engineer
Tata Consultancy Services Limited
Bangalore,Karnataka
India
Mailto: [EMAIL PROTECTED]
Website: http://www.tcs.com
Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you |
ForwardSourceID:NT00005A5A
Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you |
ForwardSourceID:NT00005AF2
Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you |