Importing XSL file in Appearance XSL.

I am designing a component in which I am putting all my Appearance XSL logic in a seperate XSL file(e.g News.xsl).
I am keeping this XSL file in content branch.
Now I want to import this xsl file in my component(News.component). How will I achieve this?

My second question is , Is this design correct. In which I am seperating the Appeance XSL code to a seperate XSL File?

Find more posts tagged with

Comments

Stokes

There is a build-in URI, http://www.interwoven.com/custom/, that does what you need. So where you see the default includes:

  <xsl:include href="http://www.interwoven.com/livesite/xsl/HTMLTemplates.xsl"/>
  <xsl:include href="http://www.interwoven.com/livesite/xsl/StringTemplates.xsl"/>

You can add yours like this:
  <xsl:include href="http://www.interwoven.com/custom/resources/xsl/News.xsl"/>

That will find resources/xsl/News.xsl in your site's workarea.

Also, yes, I haven't always separated the XSL like that, but now I consider it a personal best practice. If nothing else, during development it lets you make changes and see them in the page without going through the submit-and-get-latest cycle.

Stokes.

PS--And remove those default includes from your components if you're not using the templates they provide. You'll get a little performance gain from not parsing the extra XSL.

Adam Stoller

There is a build-in URI, http://www.interwoven.com/custom/, that does what you need. So where you see the default includes:

  <xsl:include href="http://www.interwoven.com/livesite/xsl/HTMLTemplates.xsl"/>
  <xsl:include href="http://www.interwoven.com/livesite/xsl/StringTemplates.xsl"/>

You can add yours like this:
  <xsl:include href="http://www.interwoven.com/custom/resources/xsl/News.xsl"/>

That will find resources/xsl/News.xsl in your site's workarea.
...

I'm not working on a LS project, but I've seen the above mentioned in a couple of threads and wanted to make sure if I understood it correctly. Are you literally supposed to use

http://www.interwoven.com/custom/...

or should you be substituting in your own site's (or TS server's?) domain information into the URI?

nipper

deleted....

vpatel

I'm not working on a LS project, but I've seen the above mentioned in a couple of threads and wanted to make sure if I understood it correctly. Are you literally supposed to use
http://www.interwoven.com/custom/...
or should you be substituting in your own site's (or TS server's?) domain information into the URI?

Literally use http://www.interwoven.com/custom. It is just an unique namespace that LS's XML/XSL transformer is aware of and it points to your current site's context (i.e. workarea on TS and docroot on the runtime side).

Similarly http://www.interwoven.com/livesite points the XSL residing under your LSTK.

NO you are not reaching out to Interwoven's server somewhere for these XSLs :-)!

HTH!

Adam Stoller

Literally use http://www.interwoven.com/custom. It is just an unique namespace that LS's XML/XSL transformer is aware of and it points to your current site's context (i.e. workarea on TS and docroot on the runtime side).

Similarly http://www.interwoven.com/livesite points the XSL residing under your LSTK.

NO you are not reaching out to Interwoven's server somewhere for these XSLs :-)!

HTH!

Thanks for the clarification - that last part is what had me confused. Sorry to have interrupted the thread.

Migrateduser

I was quite confused by this as well when I first started using SitePublisher. Buried deeply in the SP dev manual is an explanation that what is happening is that it is using the Apache URI resolved to turn what looks like a url fetched via http into a local filesystem access.

Here's far more than you ever wanted to know about the resolver:
http://xml.apache.org/commons/components/resolver/
resolver-article.html

Unfortunately, I haven't been able to find the config file for the resolver. I assume it's buried inside a jar. It would be nice to know exactly what it is and isn't configured to resolve.

Tarp

Literally use http://www.interwoven.com/custom. It is just an unique namespace that LS's XML/XSL transformer is aware of and it points to your current site's context (i.e. workarea on TS and docroot on the runtime side).

Similarly http://www.interwoven.com/livesite points the XSL residing under your LSTK.

NO you are not reaching out to Interwoven's server somewhere for these XSLs :-)!

HTH!

Thanks for your response. At what location we will be placing these XSL files on Livesite.
Where I will be placing the XSL files on LSTK.
Is it [IW-HOME]/httpd/webapps/content_center/WEB-INF/classes/com/interwoven/xsl ??

vpatel

Is it [IW-HOME]/httpd/webapps/content_center/WEB-INF/classes/com/interwoven/xsl ??

That is where your XSLs should end up. In addition, I believe they should go under the iw-preview app as well... In any case, don't just place your XSLs there, otherwise they'll be blown away when you do a TK "build". You should place your XSLs under LSTK and then do a build and it will place them wherever necessary for you.

HTH!

Stokes

I just put them as resources in the site's workarea in TeamSite (see post above) and they're available in preview and also get deployed to the right place in LiveSite by the publish workflow.

Stokes.

Paradigm_shift

That is where your XSLs should end up. In addition, I believe they should go under the iw-preview app as well... In any case, don't just place your XSLs there, otherwise they'll be blown away when you do a TK "build". You should place your XSLs under LSTK and then do a build and it will place them wherever necessary for you.

HTH!

I copied that under LSTK . After running the TK build , XSL file is copied under the preview location and content_center location:
/iw-home/httpd/webapps/iw-preview/WEB-INF/classes/com/interwoven/xsl/
/iw-home/httpd/webapps/content_center/WEB-INF/classes/com/interwoven/xsl/

But when I do the preview Still my component is not able to render.

Paradigm_shift

I just put them as resources in the site's workarea in TeamSite (see post above) and they're available in preview and also get deployed to the right place in LiveSite by the publish workflow.

Stokes.

How can we place the Appearance XSL files as resources . this is a new thing which I have heard. can you please elaborate more on it. Thanks for your response

vpatel

I copied that under LSTK . After running the TK build , XSL file is copied under the preview location and content_center location:
/iw-home/httpd/webapps/iw-preview/WEB-INF/classes/com/interwoven/xsl/
/iw-home/httpd/webapps/content_center/WEB-INF/classes/com/interwoven/xsl/

But when I do the preview Still my component is not able to render.

How are you referencing these XSLs in your component?

vpatel

How can we place the Appearance XSL files as resources . this is a new thing which I have heard. can you please elaborate more on it. Thanks for your response

Stokes meant that you can have external XSL files in your workarea. Refer to #5 post (posted by me) for this thread and see if that clarifies it a little bit for you.

Paradigm_shift

How are you referencing these XSLs in your component?

It is working fine now . Thanks everyone .

When I was using <xsl: include> ,it was not able to Render-->:

<xsl:include href="http://www.interwoven.com/livesite/xsl/Awards.xsl"/>
<xsl:template match="/">
<xsl:apply-imports/>
<xsl:template>

But When I changed to <xsl:import> ,it worked Smiley Happy

-->
<xsl:import href="http://www.interwoven.com/livesite/xsl/Awards.xsl"/>
<xsl:template match="/">
<xsl:apply-imports/>
<xsl:template>

Stokes

Hmm... that still doesn't sound right. If it's working I won't try to complicate things, but for posterity...

If you want to maintain your XSL in your workarea without having to copy it manually to multiple WEB-INF/classes directories, you can put your XSL file in a place like:

/default/main/mybranch/WORKAREA/myworkarea/myresources/xsl/News.xsl

And then in your component use this (literal, actual) href:

<xsl:include href="http://www.interwoven.com/custom/myresources/xsl/News.xsl"/>

Stokes.