Re: XSLT compilation errors (was: Re: required on cms)

You should use environment variables to changes the XSLT processor.
http://www.redhat.com/docs/manuals/waf/rhea-ig-waf-en-6.1/ch-prod-install-prep.html#S1-PROD-INSTALL-APPLAYERS

These can be set in /usr/share/ccm/conf/envvars in a deployment setup.

-- Dennis

On Fri, 2004-04-23 at 10:50, Vadim Nasardinov wrote:
> On Friday 23 April 2004 09:56, Tom wrote:
> > Okay, I will keep trying.  I've tried 6.1.0 nightly builds from two
> > different days and I've also tried the APLAWS release and I've had the
> > same issues with all of them.  I'll keep trying.
> >
> > By the way, when checking the logs regarding the errors I get, it's
> > says that it "Failed to compile stylesheets.  2 errors detected".  Are
> > there any general possibilities why this may be happening?
> 
> Any number of things.
> 
> First and foremost, there is a possibility of a syntactic error in the
> stylesheets we ship.  Something like this:
> 
>   <xsl:temlate match="foo">
>     <strong>misspelled "template"</strong>
>   </xsl:template>
> 
> Second, some stylesheets are generated programmatically on the fly.
> See PatternStylesheetResolver.  This may produce broken stylesheets,
> if certain customizable parameters are not set correctly.
> 
> You can try changing the XSLT processor to get a better error message.
> Some of them give more informative messages than others.  The way you
> select an XSLT processor has changed a couple of times in recent
> memory.  I don't remember offhand which is the most current way of
> doing this.  Could be a parameter you set via "ccm set".  Could be an
> environment variable.
> 


-- 
Redhat-ccm-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/redhat-ccm-list
Archives: https://www.redhat.com/pipermail/redhat-ccm-list/