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

multiple preview-dir

ml372

Hi,

we have several Content-Typs for several Branches and would set a preview-dir for each branch.
but the preview-dir is not a regex, only an path attribute.

Have someone an idea, or workaround fpr this problem?

Thanks

Find more posts tagged with

Comments

Adam Stoller

Either I'm not understanding what your concern is, or you're not understanding the purpose of preview dir.

Can you exapnd on what your concern is with having a single defined preview directory?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

ml372

Hi Fish,

thanks for your comment.
Ok, my description is perhaps not clearly, i try again.

For an example we have one Content-Type for several Branches.

<category name="dn1_integration">
<locations>
<branch vpath-regex="dekanet/main/*" />
</locations>
<data-type name="standard" dcr-type="iwov">
<presentation>
<template name="dn1_integration_standard.tpl" extension="jsp">
<locations>
<branch vpath-regex=".*" preview-dir="/">
<directory dir-regex=".*" />
</branch>
</locations>
</template>
</presentation>
</data-type>

Further we have a JSP-Preview Architecture with TeamSite and Bea WebLogic 8.1.
We have a Webapp with the Context dnprodukte and one with the Context dnberatung. All JSP's in the directory dnprodukte on the branch produkte will be mapped to the bea webapp dnprodukte, and all jsp's in the directory dnberatung in an other branch beratung will be mapped (Proxy-Remapping) to the webapp dnberatung.

If the preview dir is /, the Bea will not found the preview-jsp, because he expected the context-root (directory) dnprodukte or dnberatung.

One Idea we have, is to create one data-type for each branch.

Adam Stoller

I believe you have come to the correct conclusion given your environment's requirements. I don't have a lot of experience dealing with app-server integration for preview within TeamSite (my current project uses a "preview server" so that all files are deployed and rendered as-if they were on the actual web-server docroot, but they're either in a different doc_root or on a different server, but being processed in the "normal" way by the AppServer.

Without the application server integration - I don't think you would need to worry about the preview-dir specification at all (and hence my reason for asking the question)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

stefanmaier

Hi,
we have a similar problem with two tomcat contexts (/dir1 and /dir2),
we have two different output templates (one for each context):
The contexts /dir1 and /dir2 are in the top of our workarea...

Code in templating.cfg is

<data-type name="myname" dcr-type="iwov">
<presentation>
<template name="output1.tpl" extension="jsp">
<locations>
<branch vpath-regex=".*" preview-dir="/dir1">
<directory dir-regex=".*" />
</branch>
</locations>
</template>
<template name="output2.tpl" extension="jsp">
<locations>
<branch vpath-regex=".*" preview-dir="/dir2">
<directory dir-regex=".*" />
</branch>
</locations>
</template>
</presentation>
</data-type>

So preview files are generated in the correct webapps-directory, perhaps this will help you, too.

Ciao
Stefan