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

Replicant data in .tpl file

developer2008

Hi All,

I am generating a jsp page from my dcr which is having a replicant container. Can you please let me know how to loop through the replicant data and extract the info in my tpl file. Can I use iw_iterate? If so , how?

[html]

HREF Links

Title

[/html]

Thanks for your help.

Find more posts tagged with

Comments

vpatel

I would say look at the product guides or look at the http://your-ts-server/iw/help/tst/pt

Basically you need something like this:
[HTML]

[/HTML]

vpatel

BTW, my earlier post is just a sample -- not specifc for the part of the DCT that you have posted.

developer2008

Thanks for the reply. But I already went through those docs even before posting my query. It was very confusing to understand iw_iterate. Anyways I solved my problem using perl programming and dcr list. But If any one can explain how the iw_iterate works it would be great too.

vpatel

Thanks for the reply. But I already went through those docs even before posting my query. It was very confusing to understand iw_iterate. Anyways I solved my problem using perl programming and dcr list. But If any one can explain how the iw_iterate works it would be great too.

I am pretty sure that how it works is explained in the guide/docs. But here is the summary of it:
[HTML][/HTML]
list=dcr.Content.links assumes that you have a root element called "Content" and a "replicant/container" called "links" -- (in xpath terms: /Content/links).

var="links" -- by doing this we are assigning that container a variable name (i.e. links -- we could've named it my-links or anything you want.

[HTML][/HTML]
links.URL -- will get you the value of an element URL within your current iteration of whatever "replicant/container" is being pointed by "links" variable -- we defined it above with var="links". If you named it such as: var="myLinks" then you'll use myLinks.URL.

HTH!

developer2008

Hey It worked fine and this is much simpler than using dcr list and looping through it. Thanks for clearing that up.

vpatel

Hey It worked fine and this is much simpler than using dcr list and looping through it. Thanks for clearing that up.

Glad it worked out for you

Adam Stoller

Hey It worked fine and this is much simpler than using dcr list and looping through it. Thanks for clearing that up.

I'm not sure why you think it's simpler - if anything, it's a bit more complex because the XML code that you utilize actually gets translated into Perl code behind the scenes and that code is rather obfuscated (if you use iwpt_compile.ipl with the -ocode flag you can see the resulting code).

In terms of usability, let's look at the posted example:

<iw_iterate list="dcr.Content.links" var="links">
 <a href='{iw_value name="links.URL"/}'><iw_value name="links.label"/></a><br />
</iw_iterate>

This is essentially the same as:

foreach my $links (iwpt_dcr_list('dcr.Content.links'){
    iwpt_output(qq(<a href="$link->value('URL')">$links->value('label')</a><br />\n));
}

The two methods are not that different, it's more a question of how much other stuff you do within your PT whether one is easier to handle than the other.

Glad you got it working.

developer2008

the XML code that you utilize actually gets translated into Perl code behind the scenes and that code is rather obfuscated (if you use iwpt_compile.ipl with the -ocode flag you can see the resulting code).

oooohhhh thats interesting. I didnt know about that part. I will definitely go through that too.

The two methods are not that different, it's more a question of how much other stuff you do within your PT whether one is easier to handle than the other.

Exactly, my presentation template is more complicated and I find that iw_iterate looks a bit more simple and easy to deal with if I dont have to bother about the behind scene part. But thanks for the info. It's always good to learn more.

Adam Stoller

... my presentation template is more complicated and I find that iw_iterate looks a bit more simple and easy to deal with ...

Again, it's a matter of opinion - but the more complex the PT code, the easier *I* find it to use straight Perl code - where I can write subroutines and use both CPAN and custom Perl modules to simplify the writing of the code, and to make it re-usable in multiple PTs.

With that said, however, it is still a preference, and as such you should go with whatever you feel most comfortable using.