If you??™re using a recent browser version, you??™ll see
the XML data embedded in the page.
The only similar restriction for both client-side and server-side transformations is that if a local XML file is
used for the data, both must be contained in the same folder.
In Dreamweaver, server-side XSL transformations have been developed for most of the supported server
models: ASP, ASP.NET, ColdFusion, and PHP. Only JSP is not supported.
The workflow for creating a server-side XSLT transformation is similar to that of a client-side transformation,
with a number of key differences:
1. Create an XSLT page.
2. Attach the XML data to the XSLT page.
3. Bind the XML data to the XSLT page.
4. Remove all HTML from your application page.
5. From the dynamic page, link to the XSLT page.
6. Publish both files to the Web.
7. View the dynamic page.
The primary differences pertain, as you might expect, to the server-oriented nature of the page. As noted in
the fourth step, you??™ll need to remove all HTML from your application page. This is a necessary action
because the full XSLT page already contains the HTML framework??”, , and
tags??”and to leave it in the application page would cause errors.
Another difference is the manner in which the XSLT page is connected to the data.
Pages:
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706