| Home >> All >> org >> apache >> [ xalan Javadoc ] |
Page 1 2
• org.apache.xalan: Javadoc index of package org.apache.xalan.
Package Samples:
• org.apache.xalan.lib.sql: Extension elements and functions shipped with Xalan-Java, including EXSLT functions.
• org.apache.xalan.xpath.res: Infrastructure for processing XPATH expressions
• org.apache.xalan.xpath.dtm
• org.apache.xalan.xpath
• org.apache.xalan.xpath.xdom
• org.apache.xalan.templates
• org.apache.xalan.transformer
• org.apache.xalan.processor
• org.apache.xalan.lib
• org.apache.xalan.res
• org.apache.xalan.serialize
• org.apache.xalan.trace
• org.apache.xalan.extensions
• org.apache.xalan.client
Classes:
• Redirect: Implements three extension elements to allow an XSLT transformation to redirect its output to multiple output files. It is accessed by specifying a namespace URI as follows: xmlns:redirect="http://xml.apache.org/xalan/redirect" You can either just use redirect:write, in which case the file will be opened and immediately closed after the write, or you can bracket the write calls by redirect:open and redirect:close, in which case the file will be kept open for multiple writes until the close call is encountered. Calls can be nested. Calls can take a 'file' attribute and/or a 'select' attribute in ...
• Redirect: Implements three extension elements to allow an XSLT transformation to redirect its output to multiple output files. You must declare the Xalan namespace (xmlns:lxslt="http://xml.apache.org/xslt"), a namespace for the extension prefix (such as xmlns:redirect="org.apache.xalan.xslt.extensions.Redirect"), and declare the extension namespace as an extension (extension-element-prefixes="redirect"). You can either just use redirect:write, in which case the file will be opened and immediately closed after the write, or you can bracket the write calls by redirect:open and redirect:close, in which case ...
• EnvironmentCheck: Utility class to report simple information about the environment. Simplistic reporting about certain classes found in your JVM may help answer some FAQs for simple problems. Usage-command line: java org.apache.xalan.xslt.EnvironmentCheck [-out outFile] Usage-from program: boolean environmentOK = (new EnvironmentCheck()).checkEnvironment(yourPrintWriter); Usage-from stylesheet: <?xml version="1.0"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns:xalan="http://xml.apache.org/xalan" exclude-result-prefixes="xalan"> <xsl:output indent="yes"/> ...
• AdaptiveResultTreeImpl: AdaptiveResultTreeImpl is a adaptive DOM model for result tree fragments (RTF). It is used in the case where the RTF is likely to be pure text yet it can still be a DOM tree. It is designed for RTFs which have <xsl:call-template> or <xsl:apply-templates> in the contents. Example: <xsl:variable name = "x"> <xsl:call-template name = "test"> <xsl:with-param name="a" select="."/> </xsl:call-template> </xsl:variable> In this example the result produced by is likely to be a single Text node. But it can also be a DOM tree. This kind of RTF cannot be modelled by SimpleResultTreeImpl. ...
• XSLTEngineImpl: The Xalan workhorse -- Collaborates with the XML parser liaison, the DOM, and the XPath engine, to transform a source tree of nodes into a result tree according to instructions and templates specified by a stylesheet tree. We suggest you use one of the static XSLTProcessorFactory getProcessor() methods to instantiate the processor and return an interface that greatly simplifies the process of manipulating XSLTEngineImpl. The methods process(...) are the primary public entry points. The best way to perform transformations is to use the XSLTProcessor.process(XSLTInputSource, XSLTInputSource, XSLTResultTarget) ...
• ForwardPositionIterator: This iterator is a wrapper that always returns the position of a node in document order. It is needed for the case where a call to position() occurs in the context of an XSLT element such as xsl:for-each, xsl:apply-templates, etc. The getPosition() methods in DTMAxisIterators defined in DTMDefaultBaseIterators always return the position in document order, which is backwards for XPath in the case of the ancestor, ancestor-or-self, previous and previous-sibling. XSLTC implements position() with the BasisLibrary.positionF() method, and uses the DTMAxisIterator.isReverse() method to determine whether ...
• Stylesheet: Represents a stylesheet element. All properties in this class have a fixed form of bean-style property accessors for all properties that represent XSL attributes or elements. These properties have setter method names accessed generically by the processor, and so these names must be fixed according to the system defined in the getSetterMethodName function.
• MatchingIterator: This is a special kind of iterator that takes a source iterator and a node N. If initialized with a node M (the parent of N) it computes the position of N amongst the children of M. This position can be obtained by calling getPosition(). It is an iterator even though next() will never be called. It is used to match patterns with a single predicate like: BOOK[position() = last()] In this example, the source iterator will return elements of type BOOK, a call to position() will return the position of N. Notice that because of the way the pattern matching is implemented, N will always be a node in ...
• XSLTProcessorApplet: Provides applet host for the XSLT processor. To perform transformations on an HTML client: Use an <applet> tag to embed this applet in the HTML client. Use the DocumentURL and StyleURL PARAM tags or the setDocumentURL(java.lang.String) 55 and setStyleURL(java.lang.String) 55 methods to specify the XML source document and XSL stylesheet. Call the getHtmlText() 55 method (or one of the transformToHtml() methods) to perform the transformation and return the result as a String.
• SimpleResultTreeImpl: This class represents a light-weight DOM model for simple result tree fragment(RTF). A simple RTF is an RTF that has only one Text node. The Text node can be produced by a combination of Text, xsl:value-of and xsl:number instructions. It can also be produced by a control structure (xsl:if or xsl:choose) whose body is pure Text. A SimpleResultTreeImpl has only two nodes, i.e. the ROOT node and its Text child. All DOM interfaces are overridden with this in mind. For example, the getStringValue() interface returns the value of the Text node. This class receives the character data from the characters() ...
• StylesheetComposed: Represents a stylesheet that has methods that resolve includes and imports. It has methods on it that return "composed" properties, which mean that: Properties that are aggregates, like OutputProperties, will be composed of properties declared in this stylsheet and all included stylesheets. Properties that aren't found, will be searched for first in the includes, and, if none are located, will be searched for in the imports. Properties in that are not atomic on a stylesheet will have the form getXXXComposed. Some properties, like version and id, are not inherited, and so won't have getXXXComposed ...
• TransformState: This interface is meant to be used by a consumer of SAX2 events produced by Xalan, and enables the consumer to get information about the state of the transform. It is primarily intended as a tooling interface. A content handler can get a reference to a TransformState by implementing the TransformerClient interface. Xalan will check for that interface before it calls startDocument, and, if it is implemented, pass in a TransformState reference to the setTransformState method. Note that the current stylesheet and root stylesheet can be retrieved from the ElemTemplateElement obtained from either getCurrentElement() ...
• XSLTProcessorApplet: Provides applet host for the XSLT processor. To perform transformations on an HTML client: Use an <applet> tag to embed this applet in the HTML client. Use the DocumentURL and StyleURL PARAM tags or the setDocumentURL(java.lang.String) 55 and setStyleURL(java.lang.String) 55 methods to specify the XML source document and XSL stylesheet. Call the #transformToHTML method to perform the transformation and return the result as a String.
• FuncDocument: Execute the Doc() function. When the document function has exactly one argument and the argument is a node-set, then the result is the union, for each node in the argument node-set, of the result of calling the document function with the first argument being the string-value of the node, and the second argument being a node-set with the node as its only member. When the document function has two arguments and the first argument is a node-set, then the result is the union, for each node in the argument node-set, of the result of calling the document function with the first argument being the string-value ...
• XSLTProcessor: The transformation processor -- use XSLTProcessorFactory to instantiate an implementation of this interface. It's the responsibility of the implementation (XSLTEngineImpl), collaborating with a XMLParserLiaison, the DOM, and the XPath engine, to transform a source tree of nodes into a result tree according to instructions and templates specified by a stylesheet tree. Use the process(...) are the primary public entry points. Look at the Process class main() method for for an advanced usage example. If you reuse the processor instance, you should call reset() between transformations.
• TransformerIdentityImpl: This class implements an identity transformer for SAXTransformerFactory.newTransformerHandler() > SAXTransformerFactory.newTransformerHandler() 55 and TransformerFactory.newTransformer() > TransformerFactory.newTransformer() 55 . It simply feeds SAX events directly to a serializer ContentHandler, if the result is a stream. If the result is a DOM, it will send the events to org.apache.xml.utils.DOMBuilder . If the result is another content handler, it will simply pass the events on.
• FuncDocument: Execute the Doc() function. When the document function has exactly one argument and the argument is a node-set, then the result is the union, for each node in the argument node-set, of the result of calling the document function with the first argument being the string-value of the node, and the second argument being a node-set with the node as its only member. When the document function has two arguments and the first argument is a node-set, then the result is the union, for each node in the argument node-set, of the result of calling the document function with the first argument being the string-value ...
• ProcessorVersion: Admin class that assigns a version number to the XSLTC software. The version number is made up from three fields as in: MAJOR.MINOR[.DELTA]. Fields are incremented based on the following: DELTA field: changes for each bug fix, developer fixing the bug should increment this field. MINOR field: API changes or a milestone culminating from several bug fixes. DELTA field goes to zero and MINOR is incremented such as: {1.0,1.0.1,1.0.2,1.0.3,...1.0.18,1.1} MAJOR field: milestone culminating in fundamental API changes or architectural changes. MINOR field goes to zero and MAJOR is incremented such as: ...
• VariableStack: Defines a class to keep track of a stack for template arguments and variables, since we can't simply bind the variables to templates and walk the preceding children and ancestors. The stack is delimited by context markers which bound call frames, and which you can't search past for a variable, and by element frames, which are Arg objects with the given ElemTemplateElement instead of a qname. You can search past element frames, and they accumulate until they are popped. Note: Someone recently made the suggestion that the globals should not be kept at the bottom of the stack, but should be implemented ...
• DTM: DTM is an XML document model expressed as a table rather than an object tree. It attempts to be very compact, and to support very specifically limited multitasking: users can start reading the document while it's still being generated. (A work in progress...) (***** The SAX handler calls, and the string-based XMLDocumentHandler methods, are known to be bad; they're included as hooks for the future.) DTM does _not_ directly support the W3C's Document Object Model. However, it attempts to come close enough that a subset of DOM behavior can be implemented as proxy objects referencing the DTM.
• XConnection: An XSLT extension that allows a stylesheet to access JDBC data. It is accessed by specifying a namespace URI as follows: xmlns:sql="http://xml.apache.org/xalan/sql" From the stylesheet perspective, XConnection provides 3 extension functions: new(), query(), and close(). Use new() to call one of XConnection constructors, which establishes a JDBC driver connection to a data source and returns an XConnection object. Then use the XConnection object query() method to return a result set in the form of a row-set element. When you have finished working with the row-set, call the XConnection object close() ...
• DTMProxyMap: DTMProxyMap is a quickie (as opposed to quick) implementation of the DOM's NamedNodeMap interface, intended to support DTMProxy's getAttributes() call. ***** Note: this does _not_ current attempt to cache any of the data; if you ask for attribute 27 and then 28, you'll have to rescan the first 27. It should probably at least keep track of the last one retrieved, and possibly buffer the whole array. ***** Also note that there's no fastpath for the by-name query; we search linearly until we find it or fail to find it. Again, that could be optimized at some cost in object creation/storage.
• GetOpt: GetOpt is a Java equivalent to the C getopt() library function discussed in man page getopt(3C). It provides command line parsing for Java applications. It supports the most rules of the command line standard (see man page intro(1)) including stacked options such as '-sxm' (which is equivalent to -s -x -m); it handles special '--' option that signifies the end of options. Additionally this implementation of getopt will check for mandatory arguments to options such as in the case of '-d ' it will throw a MissingOptArgException if the option argument ' ' is not included on the commandline. getopt(3C) ...
• ExtensionHandlerJavaPackage: Represents an extension namespace for XPath that handles java packages that may be fully or partially specified. It is recommended that the class URI be of one of the following forms: xalan://partial.class.name xalan:// http://xml.apache.org/xalan/java (which is the same as xalan://) However, we do not enforce this. If the class name contains a a /, we only use the part to the right of the rightmost slash. In addition, we ignore any "class:" prefix. Provides functions to test a function's existence and call a function. Also provides functions to test an element's existence and call an element.
• ProcessorLRE: Processes an XSLT literal-result-element, or something that looks like one. The actual org.apache.xalan.templates.ElemTemplateElement produced may be a org.apache.xalan.templates.ElemLiteralResult , a org.apache.xalan.templates.StylesheetRoot , or a org.apache.xalan.templates.ElemExtensionCall .
| Home | Contact Us | Privacy Policy | Terms of Service |