Building full XSLT pages
As noted earlier, Dreamweaver gives you the option to create either an XSLT fragment or XSLT page.
Although XSLT fragments are more typically used, the full XSLT page has advantages, including the capability
to transform XML data on the client side without an application server such as ASP, ColdFusion, or PHP.
Much of the information covered in the previous XSL fragment discussion applies to full XSLT pages. XML
data appears in the Bindings panel and is bound to the page in the same manner. All the objects in the
Insert bar??™s XSLT category??”including the Repeat Region and Conditional Region objects??”can and should
be used when crafting the XML data in an XSLT page.
Client-side pages
Dreamweaver??™s client-side XSL feature set is quite remarkable. With it, you can post XML data to be transformed
by an XSLT page and viewed in a modern browser, without the use of server-side code. There are,
however, a number of limitations:
n Only full XSLT pages, and not XSLT fragments, can be used.
n The XML file must be stored locally; you can??™t link to a remote XML feed.
n Both the XML and the XSLT page must be published to the same folder on the Web server.
n Only a limited number of browsers can be used to view the completed page.
Pages:
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699