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

Component XSL calls through proxy

Samir_Friend

TS/LS 7.2.1, Solaris

Hi,
I currently am doing an xsl:include for the appearance XSL in my components. The syntax is something like:
[HTML][/HTML]

The issue is that by using the above URI, I can only refer to the XSL files within my current branch. I have a global branch from which I want to refer to these XSLs in my component instances on the site pages. Is there anyway such as writing a proxy remap rule or anything with which this might be possible?

Thanks,
Samir

Find more posts tagged with

Comments

Bowker

According to page 81 of the TeamSite SitePublisher Developer Guide SitePublisher uses the resolver mechanism to resolve those names. Info can be found at:

http://xml.apache.org/commons/components/resolver/resolver-article.html

However, it talks about a catalogManager.properties files that defines the redirects and I can't find anything like that on my system.

I would be very interested if anyone knows where they hid this file.

P.S. using ../../../ (etc) didn't appear to work for me.

tec_iwov

in the cod it descibe 2 differnt includes mechanisms.

the branch one and one that you can reference globally from the classpath.

Samir_Friend

in the cod it descibe 2 differnt includes mechanisms.

the branch one and one that you can reference globally from the classpath.

Which code/doc are you referring to?

mthukral

Hi tec_iwov,

If you are mentioning code in teamsite guide then the two methods mentioned are for local workarea and classpath. There is no code for including XSL through a URL in component from a different branch.
Does anyone know how can this be achieved?

tec_iwov

those are the only options for include as you cannot override the resolver.