file system via XSLT

Hi,
In XSLT there's the function document("****") which will read a resource from the url or the file **** and make it available in the XSLT template. I would like to use this function to access DCR's on the file system from the appearance XSLT in a component. Which path should I use to get to the DCR's?
Thank you,
Bert

Find more posts tagged with

Comments

TheYann

I suppose you could use the $URL_PREFIX variable

something like this: $URL_PREFIX/templatedata/Category/DataType/data/myDCR.xml

But there's dcr datum that you could use also!

bertve

Thank you, it sounded very promising but it doesn't work:


<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
  <xsl:template match="/">
    <xsl:copy-of select="document('$URL_PREFIX/templatedata/content/productinfo/data/visaGold')"/>
  </xsl:template>

</xsl:stylesheet>

This code in the appearance XSL of a component does not return the desired DCR... Smiley Sad

Somebody another idea?

Cheers,

Bert

TheYann

Another solution is to go through an external java object for instance ...
Or read up the LiveSite Development Guide documentation about the DCR datum which is probably doing exactly what you want!

bertve

The thing is that I don't know which DCR I want to retrieve. Imagine DCR A which contains a link to DCR B. For web publishing, you need the value of some element in DCR B. You cannot use DCR B as a datum because you don't know which file DCR A references. And DCR A could reference 0, 1 or more DCR's... So it's only when processing DCR A via XSLT that you have the information you need to retrieve the other DCR's.

TheYann

Then I go back to the other solution: a call to an external java object in which you'll be able to do everything you want.
Java is cool, you should try it Smiley Wink

bertve

As I explained, the trouble is you don't know which parameter to pass to the external Java object because you don't know which non-datum DCR will be referenced.

Migrateduser

Try something like this (untested):

document('file://\y:/default/main/mybranch/WORKAREA/myworkarea/templatedata/content/productinfo/data/visaGold')

You may have security issues, depending on how your workarea permissions are set.

bertve

Thank you for your reply. This does not work.

Migrateduser

Okay, try this:
http://myserver/iw-mount/default/main/mybranch/WORKAREA/myworkarea/templatedata/content/productinfo/data/visaGold

Get it to display in a browser first, then try the document call.

TheYann

this is bad if there is a different environment where the content is going to be deployed!
That's why there are variables like $URL_PREFIX and $PAGE_LINK!!!

Plus using $URL_PREFIX is essentially doing the same as giving the hard-coded address, other than the fact that it will always be good no matter what environment!

tec_iwov

you will need to leverage the custom resolver if you have your file referenced as follows: http://www.interwoven.com/custom/[work area relative path to xsl] this will read the file from the current site work area and also resolve correctly from the runtime web root.

Basanta

Hello,

If you want to give the path that co-relate your appreance.xsl and content.xml (which is basically an DCR), then you need to go to the "Set As Default Content" button and click on it, you will be navigated to the directory path under which you have already created your DCR, I mean the xml record.

So, in the content.xml you need to hardcoded the DCR path which will be written in .......,write the DCR path hereotherwise you can choose from the "Set As Default Content" button

bertve

Hi,

Inside the Appearance XSLT this instruction actually WORKS:


<xsl:copy-of select="file://\y:/default/main/ics/WORKAREA/main/templatedata/content/productinfo/data/visaGold" />

But I understand that the path will be different depending on the context. Which is not such a problem, because the request headers can give you the context, which gives the necessary information to dynamically modify the path.

Any objections?

tec_iwov

that will not please follow the these instructions on how it import custom stylesheets. it is the only livesite supported mechanism.

"you will need to leverage the custom resolver if you have your file referenced as follows: http://www.interwoven.com/custom/[work area relative path to xsl] this will read the file from the current site work area and also resolve correctly from the runtime web root."