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; } } }

Generate output and set attributes with XSLT

tobias

Hi there,
this is with TS 6.7.1 SP1 on Solaris 10.
We used to use "regular" Perl-based presentation templates, but the customer definitely wants to switch to XSLT-style PTs.

The customer also needs to have certain Extended Attributes attached to the generated output files, mostly to use them in Interwoven Search. With the old PTs I would simply use <iw_ostream> Tags and some Perl to issue the "iwextattr" CLT on the generated output, but how about XSLT templates?
Can you think of a way to accomplish this with XSLT-style PTs?
What other possibilities are there to generate the output files and attach some EAs to them in one go?

Thanks for your help.
Tobias

Find more posts tagged with

Comments

Firenze

We have similar requirements.

There are several approaches (workflow, triggers, callServer).

We opted for callServer approach to generate the rendition and then set the extended attributes.

Side effects of the callServer approach.

1. iwgen doesn't support xsl
Workaround: We are calling Xalan processor directly.

2. Non-Os user support impacts
Workaround: callServer is executed by iwui so need to address permissions of iwui to files.

Another potential approach, would be to call out to an object from within the XSL. I have not had experience with this but I see examples of it in the xalan documentation.

tobias

Firenze, what kind of "callServer" are you using? The callServer FormAPI method?

This wouldn't work here, since we are not using FormsPublisher to create the DCRs/XML files.

I think we will go for the Workflow approach, since this allows us to be more flexible and perform any kind of operations on/with the files.

Firenze

Yes, it is callServer (FormAPI) method.

Out of curiousity, what are you using to create the DCRs?

tobias

Hello Firenze,
the XML files I was referring to as "DCRs" are actually no real TeamSite DCRs. Instead they are generated by an external application (a 3rd party WYSIWYG editor), but are stored just like regular DCRs in the "templatedata" folder's appropriate subfolders by the external application.

Still, the generation of output files from these XML files is using regular TS presentation template mechanisms, which (content-wise) is working fine.

gzevin

Hi there,
this is with TS 6.7.1 SP1 on Solaris 10.
We used to use "regular" Perl-based presentation templates, but the customer definitely wants to switch to XSLT-style PTs.

The customer also needs to have certain Extended Attributes attached to the generated output files, mostly to use them in Interwoven Search. With the old PTs I would simply use Tags and some Perl to issue the "iwextattr" CLT on the generated output, but how about XSLT templates?
Can you think of a way to accomplish this with XSLT-style PTs?
What other possibilities are there to generate the output files and attach some EAs to them in one go?

Thanks for your help.
Tobias

I guess this functionality is in rudimentary stages at the moment as the XSLT TPLs are something very new.

Potentially one could still write in Java Xalan extensions and I am sure there will be some commom classes developed that would allow for something similar to perl in older style TPLs