resultNode = checkEnvironmentUsingWhich(myContext, factoryDocument);
/** * The exsl:node-set function converts a result tree fragment (which is what you get * when you use the content of xsl:variable rather than its select attribute to give * a variable value) into a node set. This enables you to process the XML that you create * within a variable, and therefore do multi-step processing. * * You can also use this function to turn a string into a text node, which is helpful * if you want to pass a string to a function that only accepts a node set. * * The Xalan extensions MethodResolver converts 'node-set' to 'nodeSet'. * * @param myProcessor is passed in by the Xalan extension processor * @param rtf The result tree fragment to be converted to a node-set. * * @return node-set with the contents of the result tree fragment. * * Note: Already implemented in the xalan namespace as nodeset. * * @see <a href="http://www.exslt.org/">EXSLT</a> */ public static NodeSet nodeSet(ExpressionContext myProcessor, Object rtf) { return Extensions.nodeset(myProcessor, rtf); }
/** * Returns a NodeSet containing one text node for each token in the first argument. * Delimiters are whitespace. That is, the delimiters that are used are tab (	), * linefeed (
), return (
), and space ( ). * Tokens are determined by a call to <code>StringTokenizer</code>. * If the first argument is an empty string or contains only delimiters, the result * will be an empty NodeSet. * * Contributed to XalanJ1 by <a href="mailto:benoit.cerrina@writeme.com">Benoit Cerrina</a>. * * @param toTokenize The string to be split into text tokens. * @return a NodeSet as described above. */ public static NodeList tokenize(String toTokenize) { return tokenize(toTokenize, " \t\n\r"); }
/** * Returns a NodeSet containing one text node for each token in the first argument. * Delimiters are whitespace. That is, the delimiters that are used are tab (	), * linefeed (
), return (
), and space ( ). * Tokens are determined by a call to <code>StringTokenizer</code>. * If the first argument is an empty string or contains only delimiters, the result * will be an empty NodeSet. * * Contributed to XalanJ1 by <a href="mailto:benoit.cerrina@writeme.com">Benoit Cerrina</a>. * * @param toTokenize The string to be split into text tokens. * @return a NodeSet as described above. */ public static NodeList tokenize(String toTokenize) { return tokenize(toTokenize, " \t\n\r"); }
/** * The exsl:node-set function converts a result tree fragment (which is what you get * when you use the content of xsl:variable rather than its select attribute to give * a variable value) into a node set. This enables you to process the XML that you create * within a variable, and therefore do multi-step processing. * * You can also use this function to turn a string into a text node, which is helpful * if you want to pass a string to a function that only accepts a node set. * * The Xalan extensions MethodResolver converts 'node-set' to 'nodeSet'. * * @param myProcessor is passed in by the Xalan extension processor * @param rtf The result tree fragment to be converted to a node-set. * * @return node-set with the contents of the result tree fragment. * * Note: Already implemented in the xalan namespace as nodeset. * * @see <a href="http://www.exslt.org/">EXSLT</a> */ public static NodeSet nodeSet(ExpressionContext myProcessor, Object rtf) { return Extensions.nodeset(myProcessor, rtf); }
resultNode = checkEnvironmentUsingWhich(myContext, factoryDocument);
/** * Returns a NodeSet containing one text node for each token in the first argument. * Delimiters are whitespace. That is, the delimiters that are used are tab (	), * linefeed (
), return (
), and space ( ). * Tokens are determined by a call to <code>StringTokenizer</code>. * If the first argument is an empty string or contains only delimiters, the result * will be an empty NodeSet. * * Contributed to XalanJ1 by <a href="mailto:benoit.cerrina@writeme.com">Benoit Cerrina</a>. * * @param toTokenize The string to be split into text tokens. * @return a NodeSet as described above. */ public static NodeList tokenize(String toTokenize) { return tokenize(toTokenize, " \t\n\r"); }
/** * The exsl:node-set function converts a result tree fragment (which is what you get * when you use the content of xsl:variable rather than its select attribute to give * a variable value) into a node set. This enables you to process the XML that you create * within a variable, and therefore do multi-step processing. * * You can also use this function to turn a string into a text node, which is helpful * if you want to pass a string to a function that only accepts a node set. * * The Xalan extensions MethodResolver converts 'node-set' to 'nodeSet'. * * @param myProcessor is passed in by the Xalan extension processor * @param rtf The result tree fragment to be converted to a node-set. * * @return node-set with the contents of the result tree fragment. * * Note: Already implemented in the xalan namespace as nodeset. * * @see <a href="http://www.exslt.org/">EXSLT</a> */ public static NodeSet nodeSet(ExpressionContext myProcessor, Object rtf) { return Extensions.nodeset(myProcessor, rtf); }
resultNode = checkEnvironmentUsingWhich(myContext, factoryDocument);
/** * Returns a NodeSet containing one text node for each token in the first argument. * Delimiters are whitespace. That is, the delimiters that are used are tab (	), * linefeed (
), return (
), and space ( ). * Tokens are determined by a call to <code>StringTokenizer</code>. * If the first argument is an empty string or contains only delimiters, the result * will be an empty NodeSet. * * Contributed to XalanJ1 by <a href="mailto:benoit.cerrina@writeme.com">Benoit Cerrina</a>. * * @param toTokenize The string to be split into text tokens. * @return a NodeSet as described above. */ public static NodeList tokenize(String toTokenize) { return tokenize(toTokenize, " \t\n\r"); }
/** * The exsl:node-set function converts a result tree fragment (which is what you get * when you use the content of xsl:variable rather than its select attribute to give * a variable value) into a node set. This enables you to process the XML that you create * within a variable, and therefore do multi-step processing. * * You can also use this function to turn a string into a text node, which is helpful * if you want to pass a string to a function that only accepts a node set. * * The Xalan extensions MethodResolver converts 'node-set' to 'nodeSet'. * * @param myProcessor is passed in by the Xalan extension processor * @param rtf The result tree fragment to be converted to a node-set. * * @return node-set with the contents of the result tree fragment. * * Note: Already implemented in the xalan namespace as nodeset. * * @see <a href="http://www.exslt.org/">EXSLT</a> */ public static NodeSet nodeSet(ExpressionContext myProcessor, Object rtf) { return Extensions.nodeset(myProcessor, rtf); }
resultNode = checkEnvironmentUsingWhich(myContext, factoryDocument);