Re: status quo: cocoon with xsltc

Brian Johnson Wed, 05 Feb 2003 15:49:59 -0800

Did you try putting the basename variable in your main stylesheet? I haven't had a chance to load up your pipeline and try it... I'll try to check it out tomorrow to see if it works on mine. I don't know if Saxon is any faster or not, I use it because xalan starts multiple threads and interferes with transaction management for multiple XA datasources within a pipeline.

On Wednesday, February 5, 2003, at 04:12 PM, Robert Sösemann wrote:

Thats the content of include-basepath.xsl
My problems right now happen with saxon. I already said goodbye to xsltc ;-)
And even saxon doesn't to be a great deal. The pages that work, are not
faster than before.

Strange, isn't it?

<?xml version="1.0"?>

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>


<xsl:variable name="basepath">
<xsl:text>/development/</xsl:text>
</xsl:variable>

</xsl:stylesheet>
----- Original Message -----
From: "Brian Johnson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 05, 2003 4:41 PM
Subject: Re: status quo: cocoon with xsltc

Can you also post the include-basepath.xsl? Are there any other
messages in the sitemap or error log?
BTW - I am pretty sure xsltc has a bug and does not handle xsl:include
relative paths properly. This doesn't affect Saxon.
Brian

On Wednesday, February 5, 2003, at 10:29 AM, Robert Sösemann wrote:

Thanks for answering that quick.

here are snippets


sitemap:cinclude
----------------

            <map:match pattern="**item_*-view_*">
                <!-- Rohdaten holen -->
                <map:generate type="itemdata">
                    <map:parameter name="item-id" value="{2}"/>
                    <map:parameter name="view" value="{3}"/>
                </map:generate>
                <!-- auf Basis des Typs dynamisch stylen -->
                <map:act type="stylesheet-assign">
                    <map:parameter name="item-id" value="{2}"/>
                    <map:transform
src="transform/dynamic/{stylesheet-name}.xsl" type="saxon"/>
                </map:act>
                <!-- da Matcher evtl. eigenstaendig (d.h. ohne
CInclude-Aufruf)
                     Pfade bereits setzen -->
                <map:serialize type="xhtml"/>
            </map:match>

xsl:
----
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>

    <xsl:include href="../include-basepath.xsl"/>

    <xsl:template match='*|@*'>
        <xsl:copy>
            <xsl:apply-templates select='node()|@*'/>
        </xsl:copy>
    </xsl:template>

<!-- ################  ABSTRACT-Ansicht
 ################################### -->

     <!-- Abstract OHNE Direktanzeige -->
    <xsl:template match="ABSTRACT[@DIREKTANZEIGE = '0']">
        <TABLE>
            <TR>
                <TD>
                    <DIV>
                        <!-- Ueberschrift des Infoitems als Link zur
Vollansicht -->
                        <A class="abstract_ueberschrift"
href="{$basepath}{@OBERRUBRIK}/{@UNTERRUBRIK}/
item_{@ID}.html"><xsl:value-of
select="UEBERSCHRIFT"/></A>
                    </DIV>
                    <DIV class="abstract_zusammenfassung">
                        <!-- Bild des Infoitems, falls vorhanden -->
                        <xsl:if test="BILD[@SRC != 'null']">
                            <IMG class="abstract_bild"
src="{$basepath}/abstractgrafik/{BILD/@SRC}" />
                        </xsl:if>
                        <!-- Zusammenfassung des Infoitems -->
                        <xsl:value-of select="ZUSAMMENFASSUNG"/>
                        <!-- Link zur Vollansicht des Infoitems -->
                        &#160;<A
href="{$basepath}{@OBERRUBRIK}/{@UNTERRUBRIK}/
item_{@ID}.html">mehr...</A>
                    </DIV>
                </TD>
            </TR>
        </TABLE>
    </xsl:template>

    <!-- Abstract MIT Direktanzeige (Nur Anzeige der Ueberschrift und
des
TEXT Attributes -->
   <xsl:template match="ABSTRACT[@DIREKTANZEIGE = '1']">
       <DIV class="abstract_ueberschrift_direkt"><xsl:value-of
select="UEBERSCHRIFT"/></DIV>
       <DIV class="abstract_direktanzeige"><xsl:apply-templates
select="TEXT"/></DIV>
   </xsl:template>
...

----- Original Message -----
From: "Brian Johnson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 05, 2003 4:25 PM
Subject: Re: status quo: cocoon with xsltc


It looks like there might be a problem with your stylesheet. Can you
post a copy? Thanks.
Brian

On Wednesday, February 5, 2003, at 10:20  AM, Robert Sösemann wrote:

No I am using 6.5.2. The problem is that when it comes to resolving a
cinclude I get this message:

STACKTRACE= org.apache.cocoon.ProcessingException: Failed to execute
pipeline.: org.apache.cocoon.ProcessingException: Exception during
processing of cocoon://item_50-view_ABSTRACT:
javax.xml.transform.TransformerException: org.xml.sax.SAXException:
Invalid
processing instruction name (saxon:warning)

Any ideas?

Thanks for your help.
Rob
----- Original Message -----
From: "Brian Johnson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 05, 2003 1:24 PM
Subject: Re: status quo: cocoon with xsltc


I'm using the latest stable version of Saxon with no problems at all.
I've used it under both 2.0.x and 2.1. Are you using one of the
experimental releases?

On Wednesday, February 5, 2003, at 07:14  AM, Beat De Martin wrote:
I'm using Saxon as well, it seems faster than Xalan. And with Xalan I
always
had problems with the normalize-space function.
The only problem I have with Saxon is the compiling of the sitemap.
I'm using Cocoon 2.0.2.

Did you have the same problem comipiling the sitemap with Cocoon ?
Cheers
Beat De Martin
On Wed, 2003-02-05 at 20:04, [EMAIL PROTECTED] wrote:
Dear listmembers,

after a frustrating night trying to use xsltc as a faster way to
process
xsls, browsing hundreds of archieve threads, the xsltc wiki I was
not
successfull.
I was able to make it work for a subset of my xslts (those that
didn't
use parameters).
Has anybody succesfully integrated xsltc (or any other  fast xsl
compiler
into cocoon? Does anybody know about the status of integrating
xsltc
into
cocoon? Or maybe you can just give an alternative for speeding up
transfomation.
(BUT i don't want to write custom transformers by hand)
We switched our default xslt processor to saxon (the last of the 6
releases) and have been very happy with it.
Your help is very welcome!

Robert
-k.

--
If you don't test then your code is only a collection of bugs which
apparently behave like a working program.

Website: http://www.rocketred.com.au/blogs/kevin/

------------------------------------------------------------------- -
-
Please check that your question has not already been answered in
the
FAQ before posting.
<http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:
<[EMAIL PROTECTED]>
For additional commands, e-mail:
<[EMAIL PROTECTED]>
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!

-------------------------------------------------------------------- -
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>



---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>


---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>



---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>



---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>



---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>


---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: status quo: cocoon with xsltc

Reply via email to