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

how to retrive the xml by using document() in component xsl

Nageswar

Hi Techies,

I want to retrieve the xml document in component xsl by using document method. I tried the following ways.

xsl:variable name="completeDCRPathtest" /iwmnt/default/main/CustomTaxonomy/WORKAREA/workarea/ xsl:value-of select="@RelativeVPath"
xsl:variable
xsl:variable name="DcrDomxml" select="document($completeDCRPathtest)"
xsl:value-of select="$DcrDomxml"

above is working fine. but the path is hard coded with iwmnt. how to use dynamic URL path instead of iwmnt/,..., so that we can able to deploy in to different runtime servers.

I tried to put URL_PREFIX, that is also not working.

As somebody suggested like below. but i cannot able to save the component.

How can I use above code snippet , so that Interowen will resolve the xsl and display the xml document. please specify shall I need to include any namespace in the include section.

Regards,
Nageswar

Find more posts tagged with

Comments

Rick Poulin

The safest way to really make this environment- or situation-agnostic is to load the document via a Java External, and then make it available in your component's XML datasource directly. IMO, using the document() with server paths is not a solution suitable for production use, for reasons you've already encountered and others.

Nageswar

Thanks Poulin,

But according to our requirement we should not use External, If I use java external I am getting the values.

Any way I tried like following way to load the server URL & relative path.

both paths printing correct. the Problem here is the dosument is not loading if I user server IP & port which I constructed from below. But If I hard code server path like http://Hostname:IP/RelativePath then document is loading fine.

Could you please suggest me that any problem with using dynamic url like http://$CONTEXT{request.serverName}:$CONTEXT{request.serverPort}.

Please check code snippet below, instead of getting server url from java External or hardcoded URL ,Just I am getting from CONTEXT object. but it is not working.

Please check the Component xsl code attached.

Regards,
Nageswar

Rick Poulin

Please check code snippet below, instead of getting server url from java External or hardcoded URL ,Just I am getting from CONTEXT object. but it is not working.

That's because $CONTEXT and all other page token variables get evaluated AFTER your XSL code, whereas Externals get evaluated BEFORE the XSL.

But according to our requirement we should not use External, If I use java external I am getting the values.

I strongly suggest reevaluating that requirement, because it's going to be extremely limiting for any non-trivial implementation. (And the second part of your statement implies your attempted code was wrong, because this is certainly possible)

New Line Test.zip

nipper

I strongly suggest reevaluating that requirement, because it's going to be extremely limiting for any non-trivial implementation.

Rick is being nice. That requirement is boneheaded. The requirements should not restrict the developer in that manner, then they will lose functionality.

I have been on projects where they discourage the use of Perl/Externals/etc, but if it comes between required functionality and needing extra code reviews, they will deal.

Nageswar

Thank Rick,

I got the point for page tokens.

But suppose there are 10 documents are loading dynamically on the page based on rule applied.
Targetting SampleContetActionReriever class will evaluate and will display the relative paths of the documents.
Here We want to display 10 documents contents at a time.
For Each document i need to call external to load the document content while click on href link of the reletive path.

Above solution is feasible.or instead of loading document content once again , there is any other solution for loading document data?

regards,
Nageswar

Rick Poulin

Targetting SampleContetActionReriever class will evaluate and will display the relative paths of the documents.

Perhaps you missed the "Sample" part of that class name. It's there to help you understand how to build things, not to be the one and only solution. You can take that sample code as your starting point to create your own, and add (Java) code to go read the XML of each result item before handing off the XML to the component, if that's what you need to do.

cool_rash

Hi,

Why dont you combine all the documents (I presume DCT's xml) into a single XML separated by unique nodes and get them in content XML section of the component.

I have done that in my project and its working fine for me.

Cheers
RJ

Rick Poulin

I have done that in my project and its working fine for me.

You're making assumptions about his content architecture though. Although this simplifies the one narrow use case, it could spell a world of trouble for the rest of his implementation.

Generally speaking, molding your content architecture to fit a *sample* piece of code is madness, plain and simple. Build it right the first time and you won't tie yourself into a legacy of unnecessary constraints.

cool_rash

I am just assuming there are multiple DCR's and the data is needed from all the DCR's to be populated based on rules. So, if i can get the data in a single file then I can apply the logic in the component to retrieve it based on rules.

Cheers
RJ

Bowker

We do this ALL THE TIME. If you look back on my previous posts you will see that we have a strict policy on Java and updates. If we can do it in the XSL, we do.

In the XML we will reference other XML documents and will get the content using an <xsl:variable name="CONTENT" select="document(...)"/>

The first attempt at this we hardcoded in the path to the file in the template's XSL so it looked like this:

document(concat("/opt/...some long file path.../templatedata/",$dcrName))

We have since modified our site controller to pass to the template docRoot so the document call looks like this:

document(concat(/Properties/Data//docRoot,$dcrName))

(or something really close to that)