nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

XSLT - How to determine "Preivew" vs. "Generate"?

Adam Stoller

During a recent webcast on XSLT it was asked how one could determine whether the XSLT (PT) was being called in "Preview" or "Generate" mode - and the answer was something to the effect that you should be able to determine the output file name and if it begins (or contains) "zz_tst_" then it is "Preview", otherwise it is "Generate".

Sounds reasonable - unfortunately, I don't know how to retrieve the name of the to-be-generated output file within XSLT code (and there is a serious lack of documentation from Interwoven on the usage of XSLT for processing DCRs).

Does anyone here know what directive can be used to determine this information?
(For extra kudos - you can post an entire [simple] example of usage of this directive.)

Find more posts tagged with

Comments

nipper

Are you using an XSLT or a PT with IWOV_XSLT tags ?

Using the latter, you can certainly do it easily.
something like
[html]

calculate preview/generate

XSLT here

[/html]

Adam Stoller

Are you using an XSLT or a PT with IWOV_XSLT tags ?

My fault I guess - I'm talking about 6.7.1SP1 with non-OS users so this is using the XSLT pt compiler - no Perl allowed (sigh).

patrickm

My fault I guess - I'm talking about 6.7.1SP1 with non-OS users so this is using the XSLT pt compiler - no Perl allowed (sigh).

I'm evaluating this new XSLT compiler and am trying to build up a matrix of functionalities which we can do easily in TPL and how to achieve the same in XSLT with XALAN. I'm stuck on this one too, did you managed to find the output filename in your XML or did you have to write some Java or JavaScript. IWOV should really provide a Java Class that replicates most of the iwperl system calls, so getting and reading EAs etc wouldn't require us to write our own for this.

Adam Stoller

I'm evaluating this new XSLT compiler and am trying to build up a matrix of functionalities which we can do easily in TPL and how to achieve the same in XSLT with XALAN. I'm stuck on this one too, did you managed to find the output filename in your XML or did you have to write some Java or JavaScript. IWOV should really provide a Java Class that replicates most of the iwperl system calls, so getting and reading EAs etc wouldn't require us to write our own for this.

The response I got was:[indent]... there is a java extension class that should provide this info. Unfortunately there seems to be a bug with the getOutputFileName() function and it is returning null for both preview and generated files, ... [filed as] Bug # TS-7745. A fix will be released in 6.7.2 SP1 ...[/indent]I haven't had to deal with this seince after I made the original posting, and I don't believe SP1 has yet come out, so ... I'm not sure if there's a good solution yet.

nipper

672 SP 1 is due in May (I think). There are some really cool new additions in this SP, so it is not a simple patch release

patrickm

672 SP 1 is due in May (I think). There are some really cool new additions in this SP, so it is not a simple patch release

This as usual leads to confusion. At the user group last month in London, I was told there would be no need to upgrade to SP1, to wait for TS7. SP1 wasn't meant to add major new functionality.

The more I play with this XSLT compiler, the more I feel it's a quick and amateur bolt on to support the Java direction of TeamSite.

I've been trying to generate files via the command line using recommended xalan c:
java org.apache.xalan.xslt.Process -IN foo.xml -XSL foo.xsl -OUT foo.out and that is a mess. Going to post a separate thread on that.

IWOV should be providing us with complete Java Classes to help with the migration. In all my TPLs I get and set EAs using the -X attribute. It's going to be a nightmare to reproduce this in Java/XSLT. TPL's are used for more then just generating HTML, we set attributes, create directories and set permissions etc.

As for documentation, not sure where the getOutputFileName() class is defined. I can't find it on the sample extension class unless it's in some other class.

CRB

In all my TPLs I get and set EAs using the -X attribute. It's going to be a nightmare to reproduce this in Java/XSLT. TPL's are used for more then just generating HTML, we set attributes, create directories and set permissions etc.

i am not sure how complex what you trying to acheive is but from what i understand:

to generate content using xslt and manage EA, i have an external task / perl script, which invokes the xalanTransformer with DCR PT and Output file. then manually set the EA and do other things.

the thing to keep in mind that xalanTransform (cmd) doesnt support everything the action menu/generate supports, they are using 2 different xsl compilers so whatever works using the generate command might not work when using xalanTransform. i have been using this xsl based templates because we wanted to eventually convert things to livesite components. so far i have been able to acheive everything i need. it does require more code writting than perl based template does but at the end it we acheive what we want.

as for preview vs generate, i had to write two PTs one for preview which is set in templating.cfg and another (every similar to preview template by has dynamic fields) which i use with xalantransform cmd. the generate button is removed from the DCT form (on preview is available), and the user has to use a workflow to generate pages which invokes the xalantransformer.

patrickm

i am not sure how complex what you trying to acheive is but from what i understand:

to generate content using xslt and manage EA, i have an external task / perl script, which invokes the xalanTransformer with DCR PT and Output file. then manually set the EA and do other things.

Interesting, so you've an IPL which performs the generations based on the xalanTransformer (gathering this is the same as java org.apache.xalan.xslt.Process) then set EAs on the generated files using the same IPL.

IWOV really need an formal command line interface for generating. Using XALAN, it bypasses all the rules in templating.cfg, i.e. locations for generation and file type. I've also noticed that if you attempt to iwregen a file generated with an XSL, the output is the XSL itself. iwregen appears to have a bug. And finally, I've noticed the XALAN tranformation fails if the dtd for the DCR is not correct. Can't seem to fix that one.

CRB

from my experience, the xalanTransformer that comes with TS is the available xalantransformer for the public. it doesnt have anything to do with TS or IWOV tech. it doesnt know anything about templating. it is basic xsl compiler which takes an xml (dcr) and a xsl (pt) as arguments and produces any output file you want (usually html).

yes my ipl does all that.. but it is basic perl script using the ctl cmds and alot of code. right now it is the main tool used to generate the entire corporate website till we migrate everything to liveSite.

globalvariable.bmp

oduiubo

I am doing that by file name examination of the stream.

[HTML]
 my $ptfile = iwpt_get_ofile_name(); my $ptuser = $ENV{"IW_USER"}; my $ptmode = ($ptfile =~ m/zz_tst\\_$ptuser\\_/) ? 0 : 1; if ($ptmode) { # generate } else { # preview } 
[/HTML]

patrickm

I am doing that by file name examination of the stream.

[HTML]
 my $ptfile = iwpt_get_ofile_name(); my $ptuser = $ENV{"IW_USER"}; my $ptmode = ($ptfile =~ m/\\_$ptuser\\_/) ? 0 : 1; if ($ptmode) { # generate } else { # preview } 
[/HTML]

But you can't execute IW_PERL blocks in XSL code. This isn't a TPL, you can use Java exposed via a compiled class or inline JavaScript only.

headers.rptdesign

oduiubo

When Java class with bug - JavaScript left. No other chooses.

Adam Stoller

When Java class with bug - JavaScript left. No other chooses.

What you posted was not Java, nor was it javascript - it was Perl code embedded within a Perl-based PT - which, as patrickm pointed out, was not the focus of this thread. The focus of this thread is how to distinguish between Preview and Generate when using only the XSLT processing engine - as would be the requirement if you were working with "non-OS Users" in 671SP1 or later versions of TS.

kirthi

did anyone finally manage to get the file name in xslt. Please can you provide the static method with the package name.

Thanks

kirthi

ok. Got it. For future reference

com.interwoven.cssdk.transform.XSLTExtensionContext.getContext().getOutputFileName()

Thanks

amolbho

com.interwoven.cssdk.transform.XSLTExtensionContex t.getContext().getOutputFileName()

are you using this in XSLT?

if yes can you please let me know how... am also trying same thing to achieve from XSLT.

Thanks in advance.

kirthi

Use the java extensions logic in xslt.

1. Create a Java class with a static function which returns the above output as string.

2. Inside xsl add a namespace with a reference to the class

xmlns:context="com.something.MyClass">

3. within the code call the static method

Thanks

mgammon

Thanks kirthi for posting method.

[php]

[/php]
Outputs:
1359730485941_mgammon_preview.html

Which can be used to determine "isPreview".

mgammon

Just poked around in XSLTExtensionContext and found this gem:

[php]

[/php]
Outputs:
-------------------> true