How to Generate multiple output html from one DCR using XSLT presentation templates

Hi,

I want to generate 2 html from one DCR. I am Using xslt for generating html.
I am using xalan processor for generating.

Any pointers please.

Thanks in Advance,
Tiru.

Find more posts tagged with

Comments

motlnt

You can generate multiple output files using the iw_ostream tag.
I havent tried it with XSLT based TPLs yet.

Let me know if this helps.

vpatel

You can do this in XSL PTs through XSLT Extensions. One of the many reasons people choose to go with XSL PT over TPL is that it allows you to use industry-wide technology -- there is nothing proprietary here and XSLT Extensions are no different. You can write your own custom extension to do this. Alternatively you can use Xalan's "Redirect" extension. Here is a sample:


<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" 
    xmlns:redirect="http://xml.apache.org/xalan/redirect"
    extension-element-prefixes="redirect">

<xsl:template match="/">          
 <html>
   <body>
     <xsl:value-of select="title"/>
    <redirect:write select="secondary-output.html">      
   <xsl:value-of select="node/to/secondary/output"/>      
    </redirect:write>
   </body>
 </html>
</xsl:template>


</xsl:stylesheet>

*title* field will go to your primary output file and *node/to/secondary/output* will go to secondary-output.html.

HTH!

jasonmcneil

Hi vpatel,

I just tried doing exactly what you specified in TS 7.2.1, do you know if that should output the secondary file in the same directory as the primary generated file (in the workarea)? I've tried what you posted and it unfortunately doesn't seem to create the second file, I'm wondering if these files are processed/generated in one location then moved to the workarea upon completion?

Any thoughts?

Capture du 2013-04-10 17:43:20.png

jasonmcneil

Alternatively is it possible to use Form Api to call the below line more than once in the onGenerate function?

IWPageGeneration.setOutputFile(strOutputFileName, true);

I've tried to just call it in successive lines between setting the different PT and output file name, but this doesn't seem to work either.

ShashankJain

From Form Api using call server call an ipl file and execute below mentioned code, it will generate as many no. of Output files you desire.

Eg:

my $strTplPathHtml = 'Y:/default/main/"Path of the TPl/XSLt file";
my $strhomeHtmlPath = Y:/default/main/"Path of the Output File ";
my $strAddress = "DCR Address";
$mycmd = `iwpt_compile.ipl -pt $strTplPathHtml -iw_pt-dcr $strAddress -smartwrite -iw_include-location . -ofile $strhomeHtmlPath -oenc UTF-8`;

Adam Stoller

From Form Api using call server call an ipl file and execute below mentioned code, it will generate as many no. of Output files you desire.

Eg:

my $strTplPathHtml = 'Y:/default/main/"Path of the TPl/XSLt file";
my $strhomeHtmlPath = Y:/default/main/"Path of the Output File ";
my $strAddress = "DCR Address";
$mycmd = `iwpt_compile.ipl -pt $strTplPathHtml -iw_pt-dcr $strAddress -smartwrite -iw_include-location . -ofile $strhomeHtmlPath -oenc UTF-8`;

Did you bother to read the question? Your solution is to use iwpt_compile.ipl which is for processing Perl-based PTs (a.k.a. TPLs) - the question is about being able to do this with XSLT-based PTs.

Migrateduser

Alternatively is it possible to use Form Api to call the below line more than once in the onGenerate function?

IWPageGeneration.setOutputFile(strOutputFileName, true);

I've tried to just call it in successive lines between setting the different PT and output file name, but this doesn't seem to work either.

Not sure if you got this working. If yes please let me know.
I get the title written to primary file but 2nd file is not generated.
One the I noticed is xalan.jar file is not in content-center app, not sure if this is required...it is available under /lib/xalan.jar

Thanks

jasonmcneil

Unfortunately the successive calls through formAPI didn't work out, but what did end up working was calling the "urlgenerate" url command as many times as needed.

[HTML]https://servername/iw-cc/urlgenerate?dcr=/store/main/branch/WORKAREA/workarea/templatedata/category/datatype/data/dcr.xml&pt=/store/main/branch/WORKAREA/workarea/templatedata/category/datatype/presentation/template.xsl&output=/store/main/branch/WORKAREA/workarea/outputfile.html&override=true[/HTML]

This thread has a few more details on calling this:
http://devnet.interwoven.com/forums_vb/showthread.php?t=28837&forumid=13

Adam Stoller

Unfortunately the successive calls through formAPI didn't work out, but what did end up working was calling the "urlgenerate" url command as many times as needed.

[HTML]https://servername/iw-cc/urlgenerate?dcr=/store/main/branch/WORKAREA/workarea/templatedata/category/datatype/data/dcr.xml&pt=/store/main/branch/WORKAREA/workarea/templatedata/category/datatype/presentation/template.xsl&output=/store/main/branch/WORKAREA/workarea/outputfile.html&override=true[/HTML]

This thread has a few more details on calling this:
http://devnet.interwoven.com/forums_vb/showthread.php?t=28837&forumid=13

I didn't take a look at the link, but the above seems to be answering a different question - or perhaps a different approach to what I believe is being sought.

I believe the goal is to be able to have a single DCR processed by a single XSL and result in multiple (2 or more) output files - similar to the way one can use iw_ostream in Perl-based TPL PT's to do the same thing.

Your approach would seem to suggest having a single DCR processed by multiple XSL PTs - each one designed to generate a distinct output file. While that should certainly work, it's not as "elegant" (?) as the iw_ostream concept.

jasonmcneil

Agreed, I did also try using the XSLT Redirect extension, I forget the details now, but it essentially allows you to specify a secondary output file within the XSLT and produce markup in that file.

http://xml.apache.org/xalan-j/apidocs/org/apache/xalan/lib/Redirect.html

If I remember correctly though, it would only create the secondary file relative to the processing location of the primary output file, and not the final output location. I remember stumbling across one of the output files a few weeks after attempting this and chuckling, but forget where that was since I'd already moved on.