How to link other components (with ID) into a single component

I have 4 components with different IDs. I need to create a 5th standard component where I can choose the 4 components without a need to re-write the xsl code into it. Just link and select the 4 components.

Is this possible? and how? The logic is like a frame set in html where you can link html pages on every section without a need to re-write the html code in the parent html page.

Any help will do.

Thanks.

Find more posts tagged with

Comments

Rick Poulin

You can't nest components but you can reuse XSL pieces via <xsl:include> statements. So the datums have to be recreated in your component definition but you can reuse your rendering logic. Not sure if that answers the question?

nipper

Like Rick, I am not certian I understand your question, but you can create a template which can be *part* of a page with those 4 components. You can then drop them into any new page

mm1

So if I would use <xsl:include>, then what is the target href or URI? should be the component ID (with the .seed extension)?

<!DOCTYPE html-entities SYSTEM "http://www.interwoven.com/livesite/xsl/xsl-html.dtd">
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<!-- Skin: Default (Default Browser Type) -->

<xsl:template match="/">

<xsl:for-each select="/Properties/Data/Datum/DCR/code">
<xsl:value-of select="code_label"/>
</xsl:for-each>


</xsl:template>

<xsl:include href="http://teamsite.mysite.com/iw-preview/52616e646f6d495617ef113e3ee65ffd5bad8358630062213c5bbb555668c8893711b0f3b874b14/hvy2zl40.seed" />

</xsl:stylesheet>

is this correct? i.e. I want to add the other component under the <xsl:value-of select="code_label"/>

Technically, the main goal here is to create 4 separate components and include it in one component. So, in the maintenance part, you will only update the four components but in the page template you will only include one component (which is the component that will host the 4)... The problem sometimes we need to update multiple components. This will trim down some process. Make sense?

NavinKrishna

Technically, the main goal here is to create 4 separate components and include it in one component. So, in the maintenance part, you will only update the four components but in the page template you will only include one component (which is the component that will host the 4)... The problem sometimes we need to update multiple components. This will trim down some process. Make sense?

If do a update to the component , only that will be updated not the other 4 components refernced in it and I dont think

the purpose will be served. I think the best and trouble-free way is to have them as template

Rick Poulin

LiveSite's XSL parser is configured with a URI resolver that abstracts these two things:

<xsl:include href="http://www.interwoven.com/custom/hello/world.xsl" /> will look for "[context]/hello/world.xsl" where [context] is the current workarea in preview, and is the webapp root (the runtime/web folder) on the runtime.

<xsl:include href="http://www.interwoven.com/livesite/hello/world.xsl" /> will look for "[classpath:]/com/interwoven/hello/world.xsl -- meaning you can bundle XSL as part of your build, and put them either in WEB-INF/classes or in any of your JAR files.

[...] This will trim down some process. Make sense?

Frankly, no? ... but maybe you need to play around with templates a bit first and then come back with any questions.

nipper

You are certainly not paying attention to the posts.

A template will likely meet the requirements you are suggesting.

Rick's suggestion will allow you to reuse XSL. While that is a great thing to do, it is not necessarily what you are asking about.

mm1

This include function and template did the workaround for my requirements. Thanks rpoulin!

Rick Poulin

Give nipper some kudos too, he suggested the template half of your solution Smiley Tongue