XSLT简便教程，XSLT简便教程资源-CSDN文库

需积分: 9 156 浏览量 2009-12-31 10:40:05 上传评论收藏 541KB PDF 举报

### XSLT简便教程 #### XSLT简介与核心概念 XSLT（Extensible Stylesheet Language Transformations）是一种用于转换XML文档的标准语言。通过XSLT，开发人员能够将一个XML文档转换成另一种格式的文档，如HTML、PDF或其他类型的XML文档。这在处理动态数据、生成报告或构建网站时特别有用。 #### XSLT与XPath的关系 XSLT紧密地与XPath标准配合使用。XPath提供了一种查询和定位XML文档中元素和属性的方法，而XSLT则利用这些查询结果来定义如何转换源文档。简单来说，XPath告诉你“选什么”，而XSLT告诉你“怎么做”。 #### XSLT的加工机制 XSLT的加工过程是基于树结构的。它将源XML文档解析为一棵节点树，并按照XSLT样式表中的规则对这棵树进行操作，最终生成新的节点树作为输出。这个过程通常包括以下几个步骤： 1. **加载源文档**：XSLT处理器读取并解析输入的XML文档。 2. **应用样式表**：处理器根据提供的XSLT样式表中的指令执行转换。 3. **生成结果文档**：处理器根据样式表中的规则生成输出文档。 #### 单模板样式表单模板样式表是最简单的XSLT样式表类型，它只包含一个模板，通常用于处理整个文档或者指定的特定节点。例如，可以创建一个模板来转换整个XML文档为HTML格式。 #### 理解输入和输出选项在XSLT加工过程中，理解输入和输出的选项非常重要。这包括选择合适的编码方式、设置缩进和空白字符等。通过控制这些选项，开发人员可以更精细地控制输出文档的格式和外观。 #### 多模板提高灵活性多模板样式表允许在一个样式表中定义多个模板，每个模板可以处理不同的节点类型。这种灵活性使得XSLT能够根据源文档的不同部分执行不同的转换逻辑。例如，一个模板可能专门用于处理标题，而另一个模板用于处理列表。 #### Oracle XSLT处理器的应用在实际开发中，Oracle提供了强大的XSLT处理器支持。通过命令行工具`oraxsl`、程序接口API以及XSQL页面中的`<?xml-stylesheet?>`指令，开发人员可以灵活地集成XSLT到他们的应用程序中。例如，在之前的章节中已经展示了如何使用Oracle XSLT处理器将数据库驱动的XML转换为HTML页面、特定词汇的XML数据报、SQL脚本甚至是电子邮件。 #### 实例分析考虑以下简单的XML文档示例： ```xml  <ROWSET> <ROW num="1"> <EMPNO>7839</EMPNO>  </ROW>  </ROWSET> ``` 为了将这个文档转换为HTML格式，我们可以创建一个简单的XSLT样式表： ```xslt <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="/"> <html> <body> <xsl:apply-templates select="/ROWSET/ROW"/> </body> </html> </xsl:template> <xsl:template match="ROW"> <p>Employee Number: <xsl:value-of select="EMPNO"/></p> </xsl:template> </xsl:stylesheet> ``` 在这个样式表中，我们定义了两个模板：一个用于整个文档的转换，另一个用于处理每个`ROW`节点。通过这种方式，我们能够将XML文档中的员工编号转换为HTML格式显示。 #### 结论 XSLT作为一种强大且灵活的工具，对于任何希望利用XML文档的强大功能的人来说都是不可或缺的。无论是在Web开发中还是在数据处理领域，掌握XSLT都能够极大地提高工作效率并简化复杂的数据转换任务。通过深入了解XSLT的加工机制和高级特性，开发人员可以更好地利用这一工具解决实际问题。

资源推荐

资源详情

资源评论

275

This is the Title of the Book, eMatter Edition

Chapter 7

In this chapter:

• XSLT Processing

Mechanics

• Single-Template

Stylesheets

• Understanding Input

and Output Options

• Improving Flexibility

with Multiple

Templates

Transforming XML

with XSLT

We’ve used XSLT stylesheets in previous chapters to transform database-driven

XML into HTML pages, XML datagrams of a particular vocabulary, SQL scripts,

emails, and so on. If you’re a developer trying to harness your database informa-

tion to maximum advantage on the Web, you’ll find that XSLT is the Swiss Army

knife you want permanently attached to your belt. In a world where the exchange

of structured information is core to your success, and where the ability to rapidly

evolve and repurpose information is paramount, Oracle XML developers who fully

understand how to exploit XSLT are way ahead of the pack.

XSLT 1.0 is the W3C standard language for describing transformations between

XML documents. It is closely aligned with the companion XPath 1.0 standard and

works in concert with it. As we’ll see in this chapter, XPath let’s you say what to

transform, and XSLT provides the complementary language describing how to

carry out the transformation. An XSLT stylesheet describes a set of rules for trans-

forming a source XML document into a result XML document. An XSLT processor

is the software that carries out the transformation based on these rules.

In the simple examples in previous chapters, we have seen three primary ways to

use the Oracle XSLT processor. We’ve used the oraxsl command-line utility, the

XSLT processor’s programmatic API, and the <?xml-stylesheet?> instruction to

associate a stylesheet with an XSQL page. In this chapter, we begin exploring the full

power of the XSLT language to understand how best to use it in our applications.

XSLT Processing Mechanics

An XSLT stylesheet describes a transformation that operates on the tree-structured

infoset of a source XML document and produces a tree of nodes as its output.

XSLT Processing Mechanics 279

This is the Title of the Book, eMatter Edition

As the matching template is instantiated, the following three things occur:

1. Literal result elements and attributes in the template are created in the result

tree. Result elements and attributes that are not from the XSLT namespace are

considered “literal” since they are constructed as is in the result tree. In the

example just given, the <Employee> element and its id attribute are created.

2. Any attribute value templates of the form {XPathExpr} contained within lit-

eral attribute values are replaced by the value of their XPath expression. In the

example, the {EMPNO} inside the literal attribute value NX-{EMPNO} is

replaced by the value of the EMPNO XPath expression. This evaluates to 7839,

so the final value for the id attribute in the result tree is NX-7839.

3. Any elements in the XSLT namespace are processed in document order. The

<xsl:value-of> element is processed and is replaced by a text node con-

taining the string value of the XPath expression in its select attribute—in this

case, KING.

The basic operation can be summarized as follows: when a node in the source

matches a rule’s pattern, the content of that rule is created in the result tree. Once

you grasp this basic operation, the overall XSLT processing model is easy to

understand. Given a source tree and a stylesheet, the XSLT processor carries out

the transformation described by rules in the stylesheet by following a sequence of

steps, just like the ones we have described.

A list of nodes in the source tree is processed to create a portion, or “fragment,” of

the result tree. The result tree fragment for the list of nodes is created by process-

ing the nodes in order and concatenating each of their respective result tree frag-

ments together in the same order. The node in the current node list being

processed is known, not surprisingly, as the current node. The current node is

processed by considering the set of all possible rules that match it and then select-

ing the single rule that matches it best. Only a single rule is ever used to process

the current node in the current node list.

To start the process, the XSLT processor begins with a node list containing only the

document root. It finds the template matching this root node—typically the rule

with match="/"—and instantiates the contents of the template in the result tree,

following the three basic processing steps to complete the job. If the template con-

tains elements from the XSLT namespace that select other nodes to process, the

sequence of matching and template content instantiation continues recursively until

there are no nodes left to process. When processing is completed, the result tree

represents the target document produced by the transformation.

剩余34页未读，继续阅读

评论收藏

内容反馈

pwl2014

粉丝: 1
资源: 12

XSLT简便教程，XSLT简便教程

XSLT 教程

XSLT经典教程.doc

xslt经典教程—网页设计师必备

xslt 扩展PDF教程

XSLT简单教程- XSLT的实例

XSLT 教程.doc

W3School的XSLT教程

xslt:XSLT 组件展示 [教程]

Python库 | django-xslt-0.4.3.tar.gz

python使用xslt提取网页数据的方法

XPath 教程(XPath Tutorial)多国语言帮助手册.rar

TransformBinder 工具

ＬＩＮＱ教程 轻松让你学会ｌｉｎｑ语言

XSLT_经典教程.doc

TutorialsPoint XSLT 教程.epub

XSLT参考手册（根据w3schools的XSLT教程翻译改编而成）

WAP教程(1):WAP 简介-XML/XSLT

ibatis2.X升级mybatis3.X之曲径通幽处

Umbraco 4.0.1 最新版

XML认证教程，第 5 部分_ XPATH.pdf-综合文档

第六次XML.zip

pentext:PenText系统

WAP教程(2):WAP 基础-XML/XSLT

WAP教程(6):WML 任务-XML/XSLT

WAP教程(5):WML 输入-XML/XSLT

WAP教程(9):WML 实例-XML/XSLT

WAP教程(3):WML 格式化-XML/XSLT

最新资源

ＬＩＮＱ教程　轻松让你学会ｌｉｎｑ语言