using xslt in presentation to generate html

Hi,

I am trying to use xslt to generate html file.It is working fine locally,

But when I imported to teamsite, preview is not generated it is giving error.

I made an entry in templating.cfg also.

Do I need to make any other changes .please give ur inputs.

Thanks,
Tiru.

Find more posts tagged with

Comments

Adam Stoller

Hi,

I am trying to use xslt to generate html file.It is working fine locally,

But when I imported to teamsite, preview is not generated it is giving error.

I made an entry in templating.cfg also.

Do I need to make any other changes .please give ur inputs.

Thanks,
Tiru.

You need to provide a bit more information if you want inputs:

gzevin

You need to provide a bit more information if you want inputs:
TeamSite version (including Service Pack and/or patches)
OS/Platform of TeamSite server
The error being generated
The entry you made in templating.cfg (preferably the entire clause [not the entire config file, just the clause for the specific DCT-type])
Potentially the XSL, and DCT code - but that could probably wait until the other information is provided

and also, I am not sure what was meant by 'locally'.

tiru

Thanks for your support,

I am providing the required information.

Patch ID:70516
Interwoven TeamSite 6.7.1.0 Patch 70516
Installed on:Jan 23, 2008

OS platform: windows
Error msg: An error occurred in utility daemon. Error code: 5. Please see details in iwutild.log
( No details are provided in log file )

Entry in Templating.cfg:
-------------------------
<--data-type name="catalogue" dcr-type="iwov"-->
<--presentation-->
<--template name="presentation.xsl" extension="html" ptcompiler="com.interwoven.ui.formspub.utils.XSLTPTCompiler"-->
<--locations-->
<--branch vpath-regex=".*" preview-dir="/"-->
<--directory dir-regex=".*" /-->
<--/branch-->
<--/locations-->
<--/template-->
<--/presentation-->
<--/data-type>-->

I am converting generated xml (dcr) to html using xsl out of interovwen.
it is working fine.

< -- >

Jcse

Thanks for your support,

I am providing the required information.

Patch ID:70516
Interwoven TeamSite 6.7.1.0 Patch 70516
Installed on:Jan 23, 2008

OS platform: windows
Error msg: An error occurred in utility daemon. Error code: 5. Please see details in iwutild.log
( No details are provided in log file )

Entry in Templating.cfg:
-------------------------

I am converting generated xml (dcr) to html using xsl out of interovwen.
it is working fine.

Kindly send the code again reflecting the entry in templating.cfg as it's not shown in the post.

Always preview your post before posting.

tiru

Entry in Templating.cfg:
-------------------------
<--data-type name="catalogue" dcr-type="iwov"-->
<--presentation-->
<--template name="presentation.xsl" extension="html" ptcompiler="com.interwoven.ui.formspub.utils.XSLTPTCompiler"-->
<--locations-->
<--branch vpath-regex=".*" preview-dir="/"-->
<--directory dir-regex=".*" /-->
<--/branch-->
<--/locations-->
<--/template-->
<--/presentation-->
<--/data-type>-->

pls see the code....

Appreciate ur help

Jcse

As you are using dcr-type=iwov that is the problem ,

In case of dcr-type=iwov ,xslt template will create problem,as it reads xml for implementing the presentation to generate the desire output.In you case you have defined you dcr-type=iwov which is not an xml and also it is being used earlier.So

Use

dcr-type=xml
Reformat the dct.

dcr-type=xml

HTH

tiru

Hi,

When I change the entry in templating .cfg,
I am getting error while parsing -datacapture.cfg. as
"There must be one and only one element."
<%--
<--?xml version="1.0" encoding="UTF-8"?-->
<--!DOCTYPE datacapture SYSTEM "datacapture5.0.dtd"-->
<--data-capture-requirements type="content" name="template"-->
<--ruleset name="sample"-->
<--description-->
Template to create content for the Footer Links.

<--container name="MetaData"-->
Meta Information
This will accept the meta information for the content
<--item name="title"-->
<--label-->Title
<--description-->The title to be displayed in the content
<--text maxlength="50" required="f" size="40"--/>

<--item name="description"-->
<--label-->Description
<--description-->The Meta description
<--textarea cols="40" rows="5" required="f" maxlength="200"--/>

<--item name="keywords"-->
<--label-->Keywords
<--description-->The keywords as part of meta information
<--textarea cols="40" rows="5" required="f" maxlength="200"--/>

--%>

tiru

[QUOTE=tiru]Hi,

When I change the entry in templating .cfg,
I am getting error while parsing -datacapture.cfg. as
"There must be one and only one element."
[/<%--
<--?xml version="1.0" encoding="UTF-8"?-->
<--!DOCTYPE datacapture SYSTEM "datacapture5.0.dtd"-->
<--data-capture-requirements type="content" name="template"-->
<--ruleset name="sample"-->
<--description-->
Template to create content for the Footer Links.

<--container name="MetaData"-->
Meta Information
This will accept the meta information for the content
<--item name="title"-->
<--label-->Title
<--description-->The title to be displayed in the content
<--text maxlength="50" required="f" size="40"--/>

<--item name="description"-->
<--label-->Description
<--description-->The Meta description
<--textarea cols="40" rows="5" required="f" maxlength="200"--/>

<--item name="keywords"-->
<--label-->Keywords
<--description-->The keywords as part of meta information
<--textarea cols="40" rows="5" required="f" maxlength="200"--/>

--%>QUOTE]

pls share the sample datacapture.cfg and presentation.xsl if any

Adam Stoller

I think you need to provide the XSL and DCT code (preferably as .txt attachments to avoid worrying about the formatting being interpreted by the Forum software) - however, my guess would be that you need to make sure that the XSL is written explicitly for "iwov" style DCRs - look at the example in Appendix H of the FormsPublisher Developers' Guide - you need to reference attribute values in order to access the correct elements of your DCRs.

While I believe it's easier / more straight-forward to use XSL on "xml" style DCTs - it should work with "iwov" style DCTs too.

gzevin

In you case you have defined you dcr-type=iwov which is not an xml and also it is being used earlier.

you are wrong on both assertions.

iwov type is still an XML file. The main difference is that it uses attrbutes instead of tags. And it's still being used in many occasions, maybe not so widely.

as Fish has mentioned, there is a way to treat either of DCR formats using XSLT.

Jcse

you are wrong on both assertions.

iwov type is still an XML file. The main difference is that it uses attrbutes instead of tags. And it's still being used in many occasions, maybe not so widely.

as Fish has mentioned, there is a way to treat either of DCR formats using XSLT.

Hi
Thanks for correcting me .

tiru

Hi,

Thank you very much for your support,

I was not able to understand the concept accurately
please find the attached
1. datacapture.cfg .
and correscponding
2. presentation xsl.
and guide me the correct way of writing them.

please tell me if there are any mistakes in them

vy8359

I dont think there is anything with dct or xsl. I am guessing its some mismatch with yourtemplating.cfg category/workarea category. To understand concept you need some TS background/xml/XSL. Did you create dcr using this dct ? did you try to preview ? Post your test dcr and templating.cfg section with category.

Adam Stoller

Hi,

Thank you very much for your support,

I was not able to understand the concept accurately
please find the attached
1. datacapture.cfg .
and correscponding
2. presentation xsl.
and guide me the correct way of writing them.

please tell me if there are any mistakes in them

As mentioned - I think you need to take a closer look at the DCR not the DCT, when debugging your XSL (which I believe is wrong in this case)
For one thing, I don't think you want the for-each loop
For another thing, I think your xpaths / selectors are incorrect.

Try making something work for one instance of the replicant
Then make sure it works for two (or more) instances of the replicant
If you don't already have one, find and use an XML/XSL program that allows you to quickly edit the XSL and test it (I use editix on the Mac)