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

Custom compiler for XSL

namithapai

Since I cannot search the forum for existing Q&A, and I did not get too much info from the manuals, I am asking the question here.

Does anyone have more details on how to enable a custom XSLT compiler for formspublisher?

So far, I have read:

1. Create a custom compiler jar file.
2. Add the entire path of the file in templating.cfg
3. Generate page.

Looks too simple. Someone on our team will be trying that soon, but any information will be appreciated. Such as documents, forum posts,best practices, reasons not to do it etc.,

Thanks in advance

Find more posts tagged with

Comments

Adam Stoller

Since I cannot search the forum for existing Q&A, and I did not get too much info from the manuals, I am asking the question here.

Does anyone have more details on how to enable a custom XSLT compiler for formspublisher?

So far, I have read:

1. Create a custom compiler jar file.
2. Add the entire path of the file in templating.cfg
3. Generate page.

Looks too simple. Someone on our team will be trying that soon, but any information will be appreciated. Such as documents, forum posts,best practices, reasons not to do it etc.,

Thanks in advance

What version of TS?
If you're using 6.7.1 SP1 or newer - you shouldn't need a "custom" XSLT compiler unless there's something about the one provided OOTB that doesn't work for you (if so, enquiring minds would like to know what/why).

The documentation for using it is in the FormsPublisher Developers Guide (e.g. page 74 of the 6.7.1SP1 version of the document)

namithapai

Yes we are on 6.7.1 SP1.

I don't know much about Java and its workings. Basically we need to generate JSP's that have JSP tags written out that include other jsp's etc

Our Java person believes that using a different compiler may solve our problems with CDATA, output escaping etc etc.

You have given me some food for thought and I will go back to see what exactly is the reason we cannot use the OOTB compiler and update the forum.

As for the Documentation, I did find the same section and it is quite brief.

"The two PT compilers described in the previous sections
(com.interwoven.ui.formspub.utils.PerlPTCompiler and
com.interwoven.ui.formspub.utils.XSLTPTCompiler) are the only PT compilers
included with FormsPublisher. If you write a custom compiler, you can specify
that it be used instead by specifying its full path in the ptcompiler attribute."

is all that is says, which I thought was what it alluded to in my first post.