Show navigation | Frontpage | Contact us | Sitemap

Data Query XSL Definitions

The Data Query XSL Definitions Plug-in enables developers and designers to create and maintain XSL documents used to transform Data Query results into HTML.

Walkthrough example

See how you can use this plug-in to create modules: Presenting data from a database and Generating pure XML output.

All queries defined by the Data Query Definitions Plug-in can be persisted as XML and can as such be transformed into HTML through XSL transformation. This plug-in lets you specify which queries you wish to recieve (XML) data from and what the XSL should look like. In effect this plug-in lets you publish query results with the power of XSL.

Run time info

Besides from queries you can recieve XML that represents data from

  • The Request.QueryString collection (GET data)
  • The Request.Form collection (POST data)
  • The Request.ServerVariables collection (users IP, users NT login etc.)
  • The Request.Cookies collection
  • The Session variables collection (please note that sessions are disabled on the render module by default)
  • The Application variables collection
  • The Composite run time values (current document id, current language code etc.)

You can recieve XML from any combination of the above and the queries defined by the Data Query Definitions Plug-in.

Click here to see Runtime info XPath examples.

Data Queries

The complete list of queries defined by the Data Query Definitions Plug-in, grouped by data connection. Checking one or more queries will give you access the their XML.

Click here to see Data Query XPath examples

Cache duration

If you specify a cache duration, the Cache Manager will use the run time values of the combined query parameters to store and look up data. Only parameters are used in creating this look up value - data from "Run time info" is not used. As such, you should not use caching if you reference user specific values, like cookies, unless those values are part of the query parameters.

The Cache Manager will cache the HTML result generated by the XSL transformation. Typical elements to cache are menus, site maps and other site, area or page specific elements.

Language specific XSL

For each active language there is a XSL editing area where you specify the XSL that should transform the query / run time info XML into HTML.

Get a debug view of the XML at runtime

You can easily get a complete view of the XML handed to your XSL. Emit a <Debug /> element as part of your XHTML output and the element will be replaced by a "show xml" when previewed. See Render XML debug view for more information.

My modules


© 2008 Composite A/S, Danmark
Tlf: +45 39 15 76 00 | info@composite.net
Composite A/S er Microsoft Certified Partner
Composite CMS overholder standarden for valid CSS
Composite CMS overholder standarden for valid XHTML 1.0
Printet fra http://www.composite.net/composite-564.htm
Findes på denne sti: Composite Developer | 3.x technologies | XSLT | Plug-in documentation | Data Query XSL Definitions