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

creating TPL without Perl

nirjari

I am creating TPL using xsl.
In the CDATA section, if I want to use Java instead of Perl, is that possible ?
There is nothing I can not do with Perl, that I can do with Java. Thing is, we have been using Java a lot in JSPs and other applications.

So its easier to keep up with Java everywhere, rather than going with Java there and Perl here.

If I can use Java in TPL, how can I do it ? What customization or configuration will be required ?

Thanks

Find more posts tagged with

Comments

Adam Stoller

I am creating TPL using xsl.
In the CDATA section, if I want to use Java instead of Perl, is that possible ?
There is nothing I can not do with Perl, that I can do with Java. Thing is, we have been using Java a lot in JSPs and other applications.

So its easier to keep up with Java everywhere, rather than going with Java there and Perl here.

If I can use Java in TPL, how can I do it ? What customization or configuration will be required ?

Thanks

Your choices for Presentation Templates (PTs) are currently:

RonaldV

Teamsite (and Livesite) use xalan-j for xsl-transformations.

Xalan is well documented and the documents (with examples !!!) about custom extensions can be found here: http://xml.apache.org/xalan-j/extensions.html

If you take some time to sit down and try out some sample code it is not to difficult.

But 1 general warning: xsl has lots of built-in tricks/extension to do lots of complex things. I would first take a look at these before writing your own extensions.

Adam Stoller

Teamsite (and Livesite) use xalan-j for xsl-transformations.

Xalan is well documented and the documents (with examples !!!) about custom extensions can be found here: http://xml.apache.org/xalan-j/extensions.html

If you take some time to sit down and try out some sample code it is not to difficult.

But 1 general warning: xsl has lots of built-in tricks/extension to do lots of complex things. I would first take a look at these before writing your own extensions.

Also keep in mind that TS (at least prior to 7.0 - haven't checked in 7.2 yet) uses XSLT 1.0 not 2.0 - and there are a lot of nice features in the newer version that you cannot use in TS.

awizardly

There are actually very few XSLT 2.0 transformers out there.
The folks maintaining Xalan never really finished XSLT 2.0 support.

The only parser out there that I would really trust with production code right now is Saxon. Saxon is great, it's cross platform because it is in Java, but it's not free for Autonomy to include in TeamSite. There are some beta implementations that are being developed by Intel and Microsoft, which are predictably locked to their corresponding platforms.

Ironically if you want to run Saxon in TeamSite for XSLT 2.0, it would be best to write a perl TPL that shells out and runs Saxon via a JVM on your files.

Now how's that for being twisted?