cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <>
Subject RE: ESQL Return Values & Attributes
Date Fri, 28 Sep 2001 23:00:40 GMT
MessageIf your one-pass is slow, consider splitting into several XSL
passes - to make it faster.
Some XSL calculations are faster when you do it in several simple steps
insteadof one complex step.

Also, if you have static or rarely modified parts in your XML, rely on
aggregation and Cocoon cache.

For example, always make personalization XSL as a separate last step, then
result of all previous steps
could be cached (if using static XML or XSP with defined caching methods)

for XSP caching

  -----Original Message-----
  From: Luke Reeves []
  Sent: Friday, September 28, 2001 6:35 PM
  To: ''
  Subject: RE: ESQL Return Values & Attributes

  I considered that, but a one-pass XSL transform is slow enough without
layering on another.
    -----Original Message-----
    From: Vadim Gritsenko []
    Sent: September 28, 2001 6:29 PM
    Subject: RE: ESQL Return Values & Attributes

    One way is two split your growing XSL onto two XSL, and first XSL would
    <a href=" <esql:return value here/>">
    out of data extracted from SQL, and second XSL would do whatever it does

    If there is another way, let ESQL experts tell us....

      -----Original Message-----
      From: Luke Reeves []
      Sent: Friday, September 28, 2001 6:18 PM
      To: ''
      Subject: ESQL Return Values & Attributes

      I've been building a site using Cocoon, and the ESQL tag library has
blown me away, really cool stuff.  For most of my code I do this:

          <esql:query>select id,name,shortname,homepage from projects order
by name</esql:query>
                <catshort><esql:get-string column="shortname"/></catshort>
                <catlink><esql:get-string column="homepage"/></catlink>
                <catname><esql:get-string column="name"/></catname>

      Building the site based on data encapsulated by XML tags.  But many
times, I'll want:

        <a href=" <esql:return value here/>">

      Now obviously that won't work.  But I do want to be able to access the
SQL data from an attribute of a tag; otherwise my XSL sheets grow and grow
as I break a complex single tag into multiple tags to handle little pieces
of data everywhere.  Any ideas?  Thanks in advance!

              Luke Reeves, Director of Development
              Oceanlake Commerce Inc.

View raw message