You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@locus.apache.org on 2000/03/16 19:50:23 UTC
cvs commit: xml-xalan/xdocs/sources/xalan BUGS DONE STATUS commandline.xml dtm.xml extensions.xml faq.xml getstarted.xml javadocOverview.xml org-apache-xalan-xpath-dtm.xml readme.xml resources.xml samples.xml usagepatterns.xml
dleslie 00/03/16 10:50:22
Modified: xdocs/sources/xalan Tag: Bxalan_1_0_0 BUGS DONE STATUS
commandline.xml dtm.xml extensions.xml faq.xml
getstarted.xml javadocOverview.xml
org-apache-xalan-xpath-dtm.xml readme.xml
resources.xml samples.xml usagepatterns.xml
Log:
Checked spelling. Preliminary drafts for STATUS, DONE, and BUGS; i.e., to be filled in!
Revision Changes Path
No revision
No revision
1.2.2.1 +2 -133 xml-xalan/xdocs/sources/xalan/BUGS
Index: BUGS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/BUGS,v
retrieving revision 1.2
retrieving revision 1.2.2.1
diff -u -r1.2 -r1.2.2.1
--- BUGS 2000/03/07 00:44:01 1.2
+++ BUGS 2000/03/16 18:50:07 1.2.2.1
@@ -1,137 +1,6 @@
<s3 title="Known bugs in the current Xalan version">
- <p>We are aware of the following bugs in the current version 0.20.0:</p>
+ <p>We are aware of the following bugs in version 1.0.0:</p>
<ul>
- <li>DMAN4DXQLE: Mistaken use of I instead of or causes crash
-
- </li>
- <li>DMAN4FERJ3: Number format patterns should act the same whether 1 or 2 patterns
-
- </li>
- <li>DMAN4FQJZ8: Need better argument checking for xsl:key
-
- </li>
- <li>DMAN4FQK9Z: Should flag two xsl:key keyspaces with same name
-
- </li>
- <li>DMAN4FUSQ6: Handling of null strings by contains() is not consistent across JDKs
-
- </li>
- <li>DMAN4FVS7S: Using defined constants from instance variables in switch fails in some compilers
-
- </li>
- <li>DMAN4FYS5A: Need better JavaDoc for XObject and subclasses
-
- </li>
- <li>DMAN4GBR4Z: Need nicer format to render zero as roman numeral
-
- </li>
- <li>DMAN4GBR8W: last() should insist on zero arguments
-
- </li>
- <li>DMAN4GKRZ3: Certain match patterns involving id() don't work
-
- </li>
- <li>DMAN4GLT3L: xsl:when test="" should have a specific error message
-
- </li>
- <li>DMAN4GLTN7: xsl:sort should reject all child elements
-
- </li>
- <li>DMAN4GRPXQ: Need specific error for xsl:stylesheet (or transform) not used as top-level element
-
- </li>
- <li>DMAN4GRQXY: Infinite-loop detection is not working for apply-templates with modes
-
- </li>
- <li>DMAN4GRRP6: Bad error message for elements inside xsl:decimal-format
-
- </li>
- <li>DMAN4GRS4C: Single-character attributes should raise an error when value is set longer
-
- </li>
- <li>DMAN4GRSQW: Invalid value for letter-value attribute in xsl:number should raise an error
-
- </li>
- <li>DMAN4GRTJS: Attributes count and from of xsl:number should have an error when value is not a pattern
-
- </li>
- <li>DMAN4GYUGL: Performance: should avoid calls to mult when we already know the outcome
-
- </li>
- <li>DMAN4H2RE6: namespace::xmlns not recognized as special
-
- </li>
- <li>DMAN4H3VML: Attribute values fail to override in DOM scenario
-
- </li>
- <li>DMAN4H429H: Torture test of format-number obtains garbage
-
- </li>
- <li>PDIK4D2JP5: Escaping of attribute quotes wasn't being done correctly when method="html".
-
- </li>
- <li>PDIK4D2JPR: Equality comparisons with nodesets and other nodesets, strings, and numbers not to spec.
-
- </li>
- <li>PDIK4DJS4Q: cdata-section-elements not outputing literal result element correctly
-
- </li>
- <li>PDIK4DRPKM: Use of 9/5 in a xpath expression generates a cryptic error message
-
- </li>
- <li>PDIK4E6MR3: Concat() does not check for number of arguments.
-
- </li>
- <li>PDIK4E6NZE: Stylesheet should not contain more then 1 template with the same name.
-
- </li>
- <li>PDIK4ERNDJ: Errors messages are overly verbose. Simplify where possible.
-
- </li>
- <li>PDIK4EUNA6: "xsl:element" created element does not acquire namespace prefixes from stylesheet.
-
- </li>
- <li>PDIK4FXM49: Stylesheets need to use Externalizable instead of Serializable
-
- </li>
- <li>PDIK4G5P7U: command line interface with -tt option does not output mention of built-in template for text nodes.
-
- </li>
- <li>PDIK4GBTCQ: Performance: Space stripping taking too long
-
- </li>
- <li>PDIK4GBTDY: Performance: Attributes are taking a long time to return from the DTM
-
- </li>
- <li>PDIK4GSRAB: element-available crashes if namespace prefix can not be resolved
-
- </li>
- <li>PDIK4GTR77: function-available fails if lxslt:component is not in stylesheet.
-
- </li>
- <li>PDIK4GTS2Z: function-available and element-available do not work for XSLT/XPATH components.
-
- </li>
- <li>PDIK4GTS6H: function-available crashes if namespace prefix can not be resolved
-
- </li>
- <li>SBOG4G5JCF: Need to be able to choose stylesheet via media="xxx" and type="text/xslt"
-
- </li>
- <li>SBOG4G5JF3: Need ability to do more than one XML per command line
-
- </li>
- <li>SCUU4ELPVP: Performance: XT is often faster than LotusXSL
-
- </li>
- <li>SCUU4EMMUC: ValidateXPath sample throws exception with illegal xpath
-
- </li>
- <li>SCUU4GBPJ5: org.apache.xalan.xslt.Process does not resource all strings
-
- </li>
- <li>SCUU4H3R39: [linux] JVM crashes processing lre01 (attribute in xsl namespace); all other tests run
-
- </li>
+ <li></li>
</ul>
</s3>
1.4.2.1 +7 -550 xml-xalan/xdocs/sources/xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/DONE,v
retrieving revision 1.4
retrieving revision 1.4.2.1
diff -u -r1.4 -r1.4.2.1
--- DONE 2000/03/07 01:14:06 1.4
+++ DONE 2000/03/16 18:50:07 1.4.2.1
@@ -1,566 +1,23 @@
<s3 title="Work done since the last Xalan version">
- <p>The following features were added in 0.20.0:</p>
- <ul>
- <li>Xerces 1.02 integration - This was pretty simple, just some packaging changes in the SAX2 classes.</li>
- <li>API and JavaDoc - We tried to make the API cleaner and easier to understand.</li>
- <li>Disable compilation with debug data - This cut down on the size of our JAR file by 300K or so.</li>
- </ul>
+ <p>Since Gold Candidate release 0.20.0, we have concentrated all our efforts on fixing critical bugs and upgrading the documentation.</p>
</s3>
<s3 title="Bugs Pended since the last Xalan version">
- <p>The following are Pending bugs (we think they're fixed but haven't tested them):</p>
+ <p>The following bugs have been pended (we think they're fixed but haven't tested the fixes):</p>
<ul>
- <li>PDIK4GZM3K: Calling initXPath twice in a row will cause ArrayIndexOBE due to m_tokenQueue being to small.
-
- </li>
- <li>SBOG4GYUUS: No env support to get variable, in 2nd pipe of piped transform
-
- </li>
- <li>SBOG4H3L4K: MDOCS\mdocs04, MDOCS\mdocs08, and 09 throw null pointer exception with SAX-based tests.
-
- </li>
+ <li></li>
</ul>
</s3>
<s3 title="Bugs resolved since the last Xalan version">
- <p>The following are Resolved bugs (fixed and tested):</p>
+ <p>The bugs have been fixed and tested:</p>
<ul>
- <li>DLEE4FYH9D: No support for sending primitives in extension functions
-
- </li>
- <li>DMAN465L5N: Browser hangs when running demo
-
- </li>
- <li>DMAN465LF8: Problem with relative URIs in nested import/include
-
- </li>
- <li>DMAN46GRGT: Must create a new instance of XSLProcessor for each process() call
-
- </li>
- <li>DMAN46HL8J: Empty text nodes generated when stripping whitespace
-
- </li>
- <li>DMAN46HSBF: Non-expanded entity references are lost
-
- </li>
- <li>DMAN46PTL7: CDATA treatment of character entities should follow spec painfully
-
- </li>
- <li>DMAN46PTTQ: Extra lines around output from CDATA section
-
- </li>
- <li>DMAN475K6J: Two rules for exact same pattern don't resolve as they should
-
- </li>
- <li>DMAN4D5SKA: xsl:message doesn't recognize terminate attribute
-
- </li>
- <li>DMAN4D5SPC: xsl:message puts out garbage around literal message
-
- </li>
- <li>DMAN4D5SRT: Decimal format for per-mille is not working
-
- </li>
- <li>DMAN4D5T4Z: xsl:decimal-format element not recognized
-
- </li>
- <li>DMAN4DBRUM: Compound inequality not being evaluated per spec
-
- </li>
- <li>DMAN4DHNXH: Match patterns comment() and processing-instruction() not firing
-
- </li>
- <li>DMAN4DHPF2: No way to express < or <= in a predicate
-
- </li>
- <li>DMAN4DHPJT: Numeric sorting of NaN inconsistent; spec doesn't address
-
- </li>
- <li>DMAN4DWTUK: round() not handling .5 cases per spec
-
- </li>
- <li>DMAN4E7UU8: Included stylesheets need distinguished namespaces, etc.
-
- </li>
- <li>DMAN4EFSVL: Boolean-valued lang() function emits no output
-
- </li>
- <li>DMAN4EFTBU: boolean(node-set) should return true for non-empty set
-
- </li>
- <li>DMAN4EFU46: Equality of result tree fragments fails
-
- </li>
- <li>DMAN4EFUNB: decimal-format reassignment of characters in format string has no effect
-
- </li>
- <li>DMAN4EJUUG: Default decimal-format declarations cannot be changed
-
- </li>
- <li>DMAN4ESS98: Sort with data-type="number" should only rearrange numbers.
-
- </li>
- <li>DMAN4ETPTK: case-order attribute apparently ignored in xsl:sort
-
- </li>
- <li>DMAN4FEPC5: Some xsl:sort attributes must reject bad keyword values
-
- </li>
- <li>DMAN4FFQBJ: Need correct URL in system-property
-
- </li>
- <li>DMAN4FNSEU: Need error message for xsl:choose lacking an xsl:when
-
- </li>
- <li>DMAN4FQJUL: Use of key() in keyspace causes crash
-
- </li>
- <li>DMAN4FQK48: key() has badly-formed error message when keyspace doesn't exist
-
- </li>
- <li>DMAN4FQRJL: key() should issue an error if it doesn't get exactly two arguments
-
- </li>
- <li>DMAN4FVSJG: Some bad links on Apache Xalan pages
-
- </li>
- <li>DMAN4FWUKK: key() is not creating a complete node-set
-
- </li>
- <li>DMAN4FYPWC: Descriptions missing in JavaDocs
-
- </li>
- <li>DMAN4FYQFS: Need better JavaDocs strings in XPathProcessorImpl class
-
- </li>
- <li>DMAN4FYREQ: Miscellaneous cleanup needed on Xalan API page on apache.org Website
-
- </li>
- <li>DMAN4FYSFJ: Need better JavaDoc for XSLTProcessorApplet class
-
- </li>
- <li>DMAN4FYSTE: Need better JavaDoc for XSLTProcessor Interface
-
- </li>
- <li>DMAN4GBLKN: Generated numbers sometimes have wrong format
-
- </li>
- <li>DMAN4GBMGY: Wacky numbering when level=multiple and from has only one level
-
- </li>
- <li>DMAN4GBQXL: Conversion of non-convertible string to number no longer obtains NaN
-
- </li>
- <li>DMAN4GDLHD: Strange counting in xsl:number level="any" when count path has a predicate
-
- </li>
- <li>DMAN4GDLQQ: Numbering separate levels with xsl:number level=single misses top level
-
- </li>
- <li>DMAN4GEVDF: Version number cannot be built into system-property
-
- </li>
- <li>DMAN4GHQNU: Using sort with either last() or position() in select expression crashes
-
- </li>
- <li>DMAN4GHVGP: NumberFormat09 crashes after issuing incorrect error message
-
- </li>
- <li>DMAN4GJPXR: Can crash under some conditions when variable is undefined
-
- </li>
- <li>DMAN4GJRZH: Null test in xsl:if triggers wrong error message
-
- </li>
- <li>DMAN4GKV7N: Unions in select patterns often fail
-
- </li>
- <li>DMAN4GRRTD: No error message for bad attribute in decimal-format
-
- </li>
- <li>DMAN4GSLST: Disallowed name for created PI causes runtime exception
-
- </li>
- <li>DMAN4GSM9Q: Must catch bad NCnames in xsl:element
-
- </li>
- <li>DMAN4GSP5T: Missing select on xsl:copy-of causes stack dump
-
- </li>
- <li>DMAN4GSV35: Missing name in call-template causes stack dump
-
- </li>
- <li>DMAN4GTPUZ: Xalan only: vendor name is wrong
-
- </li>
- <li>DMAN4GXR7E: Using absolute filepath for XSL file causes stack dump
-
- </li>
- <li>DMAN4GYTXG: Boolean function doesn't anticipate null input, stack-dumps
-
- </li>
- <li>DMAN4GYU8X: Garbage in test attribute of xsl:if causes stack dump
-
- </li>
- <li>DMAN4GYVXL: Numeric expressions stack-dump if an operator or function gets a null as operand
-
- </li>
- <li>DMAN4GYW5T: Functions that take string arguments should check for null (as opposed to null string)
-
- </li>
- <li>DMAN4GZ277: Functions that expect node-set will crash if they get a null instead
-
- </li>
- <li>DMAN4H2N2Z: Under DOM, lang() fails in a case where it works under DTM
-
- </li>
- <li>DMAN4H2NDH: URL-related functions fail under DOM, but okay under DTM
-
- </li>
- <li>DMAN4H3SUC: Matching on id('literal') fails under DOM only
-
- </li>
- <li>MMIY4ELLNZ: Error reporting mechanism needs major improvements
-
- </li>
- <li>MMIY4G5RKT: Need to have XSLTInputSource have a setDocumentHandler method, etc.
-
- </li>
- <li>MMIY4G5RPR: Stylesheet Attribute validation seems not to be working
-
- </li>
- <li>MMIY4G5RY5: Processor needs to be smarter about using DTM vs. Xerces liaison
-
- </li>
- <li>MMIY4G5RZU: xsl:sort should do simple string compare if lang="english"
-
- </li>
- <li>PDIK4D2JCF: Failure to parse attribute with a SPACE within quoted string
-
- </li>
- <li>PDIK4D2JLR: Problems parsing <xsl:with-param> stmt
-
- </li>
- <li>PDIK4D9RX5: FormatterToXML is throwing a NullPointerException
-
- </li>
- <li>PDIK4DASEE: Predicate test failing when testing for number that has space around it
-
- </li>
- <li>PDIK4DBTZG: method="html" failing to esc non-ASCII chars in URI attributes via HTML 4.O Spec
-
- </li>
- <li>PDIK4DHUR4: <Option selected="selected"> not being output correctly for HTML output.
-
- </li>
- <li>PDIK4DHUVS: <? Processing Instructions?> not being not being terminated correctly for HTML output.
-
- </li>
- <li>PDIK4DJSE3: xsl:output method="xsl" not outputing proper xml header for result file
-
- </li>
- <li>PDIK4DJSKZ: omit-xml-declaration is not a recognize attribute for method="xml"
-
- </li>
- <li>PDIK4DRL8E: HTML DTD being output after initial data.
-
- </li>
- <li>PDIK4DRLCG: No error reporting of invalid use of disable-output-escaping
-
- </li>
- <li>PDIK4DSKP4: Included template w/higher priority not being instantiated
-
- </li>
- <li>PDIK4DVTJS: Marginal error reporting for toplevel elements with undefined namespaces.
-
- </li>
- <li>PDIK4E4KCL: Not allowed to have xsl:apply-imports within a xsl:for-each
-
- </li>
- <li>PDIK4E8L6L: <xsl:namespace-alias stylesheet-prefix="axsl" result-prefix="xsl"/> not working correctly
-
- </li>
- <li>PDIK4E8QBB: The expression in a use attribute on xsl:key should not restricted to return a node-set.
-
- </li>
- <li>PDIK4E8UHQ: Extend tests that use Javascript not running w/ latest js.jars
-
- </li>
- <li>PDIK4EBQWT: Processor crashes running example for embedded stylesheets from spec
-
- </li>
- <li>PDIK4ECQK3: Document() not creating a union when single argument is a nodeset.
-
- </li>
- <li>PDIK4ECTX7: NPE when passing document() a nodeset of 'doc' as second argument
-
- </li>
- <li>PDIK4ECVJJ: document("") does NOTrefer to the root node of the stylesheet
-
- </li>
- <li>PDIK4ED222: exclude-result-prefixes="ped bdd #default" not working with multiple prefixes
-
- </li>
- <li>PDIK4EF2FS: xml header being output all the time
-
- </li>
- <li>PDIK4EF2KL: Doctype declaration not output html/HTML when it's suppose to.
-
- </li>
- <li>PDIK4EKLX9: Attribute sets test atrs07, seems to be generating wrong output
-
- </li>
- <li>PDIK4EKNM8: Prop01 returns the value of system-property('xsl:version') as a string not a number
-
- </li>
- <li>PDIK4ELNRC: Outp tests 19,20,21,22,23 now failing to output xml headers w/ different encodings.
-
- </li>
- <li>PDIK4ELPBD: Document()'s error resources should be in XSLT not XPATH.
-
- </li>
- <li>PDIK4ELSE3: Entref01: value-of is not passing "&" thru to result output file.
-
- </li>
- <li>PDIK4ERPLJ: $x="foo" does not mean the same as not($x!="foo")
-
- </li>
- <li>PDIK4ESQA5: LRE attribute creation will include nodes with names in the XSLT namespace.
-
- </li>
- <li>PDIK4ESQEF: both forms of exclude-result-prefixes fail to suppress the default namespace - #default
-
- </li>
- <li>PDIK4ESTEB: exclude-result-prefixes, should not apply to any included/imported stylesheets
-
- </li>
- <li>PDIK4ETKTJ: Attribute value template does not parse.
-
- </li>
- <li>PDIK4ETPCT: xsl:element name attribute should generate error if result from the AVT is not a QName.
-
- </li>
- <li>PDIK4EUQN6: LRE with namespace prefixed QName attribute(ped:attr) does not pass attribute to result tree.
-
- </li>
- <li>PDIK4EYP2U: Parameters are not evaluated by XPATH expressions correctly.
-
- </li>
- <li>PDIK4F7PZC: Should we generate namespaces if it's set to ""
-
- </li>
- <li>PDIK4F7QUC: attribute name is accepting an invalid QName and "xmlns" as valid names.
-
- </li>
- <li>PDIK4F7TP5: Using sort with position() fails.
-
- </li>
- <li>PDIK4F8N4Y: <xsl:elements> elements are not getting copy of namespace nodes from element node.
-
- </li>
- <li>PDIK4F9L5Q: Problems with whitespace stripping in stylesheet.
-
- </li>
- <li>PDIK4F9PTP: Customer problem. Attempt to create DOM output w/o creating root node first, crashes.
-
- </li>
- <li>PDIK4F9QVX: URL encoding should escape the space character as '%20'.
-
- </li>
- <li>PDIK4FBMT8: document not sucking in a document of different encoding.
-
- </li>
- <li>PDIK4FHTUQ: The xml:space attributes are not stripped from the tree.
-
- </li>
- <li>PDIK4FJNZV: Using <xsl:output indent="yes"> exclusively within a stylesheet does not perform indent.
-
- </li>
- <li>PDIK4FJR54: xsl:number fails to generate proper result if xml file has comment before doc element
-
- </li>
- <li>PDIK4FPU6T: redirect doesn't create files relative to the output file
-
- </li>
- <li>PDIK4FXLWA: Stylesheet should hold memory about the liaison it should use
-
- </li>
- <li>PDIK4FXM2R: Problem with computation of opPos -= 3; in org/apache/xalan/xpath/dtm/DTMNodeLocator.java
-
-
- </li>
- <li>PDIK4FYPHX: document() in included .xsl is based on URI of including .xsl not included .xsl
-
- </li>
- <li>PDIK4FYSLG: "version" attribute on <xsl:stylesheet> is required.
-
- </li>
- <li>PDIK4G3TVT: Expansion of entity reference is hosing numbering.
-
- </li>
- <li>PDIK4G5NUY: xsl:output attribute 'indent' not indenting non-html elements.
-
- </li>
- <li>PDIK4G6MYB: From forum: German Umlauts (ISO-8859-1) are not output to result tree correctly.
-
- </li>
- <li>PDIK4GBR22: Attributes that contain CRLF, must output a character reference for CRLF
-
- </li>
- <li>PDIK4GBR5Z: Test for the preceding::* axes are broken
-
- </li>
- <li>PDIK4GBRM4: Intl01 Fails. It use to output entity references for the correctly for Big5 encoding.
-
- </li>
- <li>PDIK4GBTA7: Performance: Depth-first search enhancement.
-
- </li>
- <li>PDIK4GBTET: Performance: SaxAttributeImpl is tooooooooooo big.
-
- </li>
- <li>PDIK4GCLA7: Processing Instruction with in a for-each loop is not being totally ignored.
-
- </li>
- <li>PDIK4GCPRG: Atrs24: It's easy to generate an attribute of the form abc:xyz:Attr="blablabla"
-
- </li>
- <li>PDIK4GCRA9: xsl:copy-of not copying elements namespace nodes that are inherited from the parent.
-
- </li>
- <li>PDIK4GCT6V: xsl:copy: missing select attribute causes crash.
-
- </li>
- <li>PDIK4GHL4C: System w/default encoding of DP-2312 (DPK), is not being overridden to UTF-8.
-
- </li>
- <li>PDIK4GHMZA: Simple LRE stylesheet not processing the version attribute correctly
-
- </li>
- <li>PDIK4GHPZ7: Basic test of xsl:copy is failing.
-
- </li>
- <li>PDIK4GHQAQ: Failure of xsl:copy to copy attributes.
-
- </li>
- <li>PDIK4GHQTH: LRE01, stylesheet attribute extension-element-prefixes is broken
-
- </li>
- <li>PDIK4GHS8L: Need to integrate with xerces 1.0.2 w/ Sax support
-
- </li>
- <li>PDIK4GKQB2: Namespace axes is not implemented
-
- </li>
- <li>PDIK4GLUPM: Overwriting previously set attributes crashing in MutableAttrListImpl
-
- </li>
- <li>PDIK4GLUVU: Attributes set tests are failing in FormatterToXML
-
- </li>
- <li>PDIK4GMLVR: NPE: Caused by sending RTF out to the DOM.
-
- </li>
- <li>PDIK4GMSHL: Slct03 failing; adding attribute to <out> when it should'nt be.
-
- </li>
- <li>PDIK4GRMZ5: Failing to match a LocationPathPattern based on an IdKeyPattern.
-
- </li>
- <li>PDIK4GRQZX: Failing to match "attribute::*" in match pattern
-
- </li>
- <li>PDIK4GRR3Q: Failing to match "child::*" in match pattern
-
- </li>
- <li>PDIK4GSQK7: XSLT element-available function not working.
-
- </li>
- <li>PDIK4GSSF5: Makefiles; cleanup?; compile with g:none, removes debug code (opt/debug builds)
-
- </li>
- <li>PDIK4GZRHZ: Element from XSLT namespace may have any attribute not from XSLT namespace provided.....
-
- </li>
- <li>PDIK4H3QXA: Invalid attributes of the form x="x", without namespace URI are not being flagged as errors.
-
- </li>
- <li>PDIK4H3TNC: xsl:attribute will allow generation of null namespace nodes.
-
- </li>
- <li>RWER4GJQHK: showtree-19991008.xsl perf benchmark crashes
-
- </li>
- <li>RWER4GJUY3: Greek numbering crashes with array bounds exception with HTML output
-
- </li>
- <li>SBOG45UMEH: Tests 43, 34: Namespace handling in patterns seems to fail in XML4J2DOM liaison
-
- </li>
- <li>SBOG45UMVJ: Test62,63: XML4J2DOM: Dropped tag end (>)
-
- </li>
- <li>SBOG4FWN66: Problem with "//a" and large docs (Inconsistent Behavior Xalan v. XT and ODI Stylus)
-
- </li>
- <li>SBOG4FWNH2: StylesheetRoot creates wrong liaison if processor is not passed
-
- </li>
- <li>SBOG4G67ZU: Stylesheet serialization is broken
-
- </li>
- <li>SCUU4D9S36: Process.java does not check for errors in command line
-
- </li>
- <li>SCUU4ELPRP: TestThreads: running processors on multiple threads throws exceptions
-
- </li>
- <li>SCUU4ELRSG: Xalan's samples\pipe does not appear to work from end-user perspective
-
- </li>
- <li>SCUU4FER9P: Documentation typos/errors in Xalan 0.19.2 Overview, etc.
-
- </li>
- <li>SCUU4GBPDY: JVM crashes processing idky14 with XercesLiaison
-
- </li>
- <li>SCUU4GBPM4: DTM.java(1517) System.out.println("Not descendent..."); - should be if(DEBUG) or something
-
- </li>
- <li>SCUU4GBRB5: Placeholder: Move doc-related README, etc. files to new xdocs structure
-
- </li>
- <li>SCUU4GTSBS: TransformToDom sample throws exception; build xalan_0_19_5
-
- </li>
+ <li></li>
</ul>
</s3>
<s3 title="Bugs closed since the last Xalan version">
- <p>The following are Closed bugs (not really a bug; no longer applicable; etc.):</p>
+ <p>We have determined that the following bug reports are not actual bugs:</p>
<ul>
- <li>DMAN465KYD: Demo page exposes possible timing issues
-
- </li>
- <li>DMAN46RS8G: Attribute-sets not interacting well
-
- </li>
- <li>DMAN4EFUYU: decimal-format pattern-separator setting has no effect
-
- </li>
- <li>DMAN4G5TLR: xsl:number assumption of separators is no longer correct
-
- </li>
- <li>DMAN4GBQTW: Null string should be a substring of itself; "contains" function defect
-
- </li>
- <li>PDIK47NLGY: xsl:stylesheet is not synonymous with xsl:transform
-
- </li>
- <li>PDIK4D2JFT: <xsl:text disable-output-escaping="yes"> not working with <xsl:output method=html>
-
- </li>
- <li>SBOG45VNAM: uri() function doesn't take into account the base uri of the stylesheet.
-
- </li>
+ <li></li>
</ul>
</s3>
1.3.2.1 +20 -15 xml-xalan/xdocs/sources/xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/STATUS,v
retrieving revision 1.3
retrieving revision 1.3.2.1
diff -u -r1.3 -r1.3.2.1
--- STATUS 2000/03/07 01:14:06 1.3
+++ STATUS 2000/03/16 18:50:08 1.3.2.1
@@ -1,16 +1,21 @@
-<s3 title="To-do tasks for future Xalan versions">
- <p>Things wed like or are planning to do in Xalan:</p>
- <ul>
- <li>Updating this STATUS file regularly</li>
- <li>This (Xalan 0.20.0) is a Gold Candidate release. Before we release this as the long-awaited Xalan 1.0.0, we'd
- like you all to bang on it a bit, especially via the API. We've done a pretty good job at testing via the org.apache.xalan.xslt.Process
- comand-line driver, but we have more limited exposure to running in more complicated run-time scenarios, especially multi-threaded, etc.</li>
- <li>We're looking at replacing our current make system with Ant for post Xalan 1.0. Shane shane_curcuru@lotus.com is looking into this.</li>
- <li>It would be great if someone would volunteer to own JBuilder support for Xalan, e.g. regularly test to make sure we
- compile and run correctly in that environment, produce project files for JBuilder for released version of Xalan, etc.</li>
- <li>Ditto for other IDE's: Visual Cafe, MSVJ++, whatever people have expertise in. Just post a note to the list if you're interested.
- The best person to maintain stuff like this is someone who works with the builder on a regular basis, and that isn't me! </li>
- <li>There's a lot of talk now about Xalan 2.0 and what that will be, including a possible top-down redesign.
- Watch the xalan-dev list for more information and to see how you can get involved.</li>
- </ul>
+<s3 title="Version of Xerces to use">
+<p>Xalan-J version 1.0.0 has been tested with Xerces-j version 1.0.3. The Xalan download from xml.apache.org and the LotusXSL download from IBM alphaWorks both include xerces.jar from Xerces-j version 1.0.3. For information about including xerces.jar on the system class path, see <link idref="getstarted" anchor="classpath">Setting up the system class path</link>.</p>
+<p><em>Important</em> You may experience unpredictable anomalies if your Xalan and Xerces builds are not in synch. If you download an update to Xalan, check the release notes to determine which version of Xerces you should use.</p>
+<note>You can use Xalan with other XML parsers, but it is up to you to implement liaisons to those parsers. Your liaison class should extend <resource-ref idref="XMLParserLiaisonDefaultDoc"/> and implement <resource-ref idref="XPathSupportDoc"/>.</note>
+</s3>
+<s3 title="To-do tasks for future Xalan releases">
+ <p>A top priority for the &xslt4j; team in the ongoing development of &xslt4j; is to improve performance. This includes
+ enhanced support for SAX and incremental transformations, more efficient trees than current implementations of the DOM
+ interfaces provide, and a number of possibilities pertaining to the compilation of stylesheets, pooling stylesheet objects,
+ preprocessing XML/XPaths, and so on.</p>
+ <p>As part of the xml.apache team, the &xslt4j; team is exploring options to upgrade the integration of all the xml.apache
+ projects, including Xalan, Xerces, Cocoon, and FOP.</p>
+ <p><human-resource-ref idref="scurcuru"/> is looking into replacing our current make system with the Java Ant
+ system.</p>
+ <p>It would be great if someone would volunteer to own JBuilder support for Xalan, that is to regularly test to make sure
+ Xalan compiles and runs correctly in that environment, produce JBuilder project files for Xalan releases, etc. Ditto for other
+ IDE's: Visual Cafe, MSVJ++, whatever people have expertise in. Just post a note to the list if you're interested.
+ Obviously, the best person to take on responsibility for testing &xslt4j; with a builder is someone who works with the builder
+ on a regular basis.</p>
+ <p>Watch the <human-resource-ref idref="xalandev"/> for more information and for ideas about how you can get involved.</p>
</s3>
1.6.2.1 +6 -6 xml-xalan/xdocs/sources/xalan/commandline.xml
Index: commandline.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/commandline.xml,v
retrieving revision 1.6
retrieving revision 1.6.2.1
diff -u -r1.6 -r1.6.2.1
--- commandline.xml 2000/03/01 18:24:32 1.6
+++ commandline.xml 2000/03/16 18:50:09 1.6.2.1
@@ -63,14 +63,14 @@
<s2 title="Using the Command-Line Utility">
<p>To perform a transformation, you can call &xslt4j; from the command line (or script),
- an applet, an application, or a servlet (see <link idref="usagepatterns">UsagePatterns</link>).</p>
- <p>The org.apache.xalan.xslt.Process main() method provides a comand-line interface
+ an applet, an application, or a servlet (see <link idref="usagepatterns">Usage Patterns</link>).</p>
+ <p>The org.apache.xalan.xslt.Process main() method provides a command-line interface
for performing XSL transformation. To perform a transformation from the command line or a script,
do the following:</p>
<ol>
<li><link idref="getstarted" anchor="download">Download &xslt4j;</link>.<br/><br/></li>
<li><link idref="getstarted"
- anchor="classpath">Set the java classpath</link> to include xalan.jar and xerces.jar<br/><br/></li>
+ anchor="classpath">Set the java class path</link> to include xalan.jar and xerces.jar<br/><br/></li>
<li>Call java and the Process class with the appropriate flags and
arguments (described below). The following command line, for example, includes the -IN, -XSL,
and -OUT flags with their accompanying arguments -- the XML source document, the XSL
@@ -116,11 +116,11 @@
you want to set the parameter to a string value, enclose the string in single quotes (') to
make it an expression.</p>
<p><anchor name="compiledstylesheet"/><em>Using a compiled stylesheet</em></p>
- <p>If you are using a stylesheet repeatedly, you can improvide performance by compiling the stylesheet the first time
+ <p>If you are using a stylesheet repeatedly, you can improve performance by compiling the stylesheet the first time
you use it and using the compiled stylesheet for subsequent transformations.</p>
<p>For example, the following command line performs a transformation and compiles the stylesheet:"<br/><br/>
- <code>java org.apache.xalan.xsltProcess -in foo.xml -xsl foo.xsl -lxcout foo.style</code><br/><br/>
+ <code>java org.apache.xalan.xslt.Process -in foo.xml -xsl foo.xsl -lxcout foo.style</code><br/><br/>
The following command line uses the compiled stylesheet for the next transformation:<br/><br/>
- <code>java org.apache.xalan.xsltProcess -in foo2.xml -lxcin foo.style</code></p>
+ <code>java org.apache.xalan.xslt.Process -in foo2.xml -lxcin foo.style</code></p>
</s2>
</s1>
1.5.2.1 +5 -5 xml-xalan/xdocs/sources/xalan/dtm.xml
Index: dtm.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/dtm.xml,v
retrieving revision 1.5
retrieving revision 1.5.2.1
diff -u -r1.5 -r1.5.2.1
--- dtm.xml 2000/03/06 13:31:48 1.5
+++ dtm.xml 2000/03/16 18:50:09 1.5.2.1
@@ -64,7 +64,7 @@
<p>The Document Object Model (<resource-ref idref="DOM"/>) provides a standard interface for interacting
with XML documents. &xslt4j; supports this interface. For large XML documents, however, this may involve considerable
overhead, since &xslt4j; must create one or more Java objects for each Node in the document DOM tree.</p>
- <p>For the majority of cases -- your input and output are URLS, files, or streams, and you use the default Liaison
+ <p>For the majority of cases -- your input and output are URLs, files, or streams, and you use the default Liaison
(<resource-ref idref="DTMLiaisonDoc"/>) and XML parser, &xslt4j; avoids this overhead by implementing the Document Table
Model (DTM), a "pseudo-DOM" that uses integer arrays in place of the DOM. For larger input and output trees, the
performance improvements can be very significant.</p>
@@ -72,14 +72,14 @@
and XML parser. If your input or output turns out to be a DOM Node, the XSLTProcessor automatically switches to the
<resource-ref idref="XercesLiaisonDoc"/> and the Xerces DOM parser. You can explicitly instantiate an XSLTProcessor to use
XercesLiaison and the Xerces DOM parser as follows:</p>
- <p><code>org.apache.xalan.xsltXSLT.Processor xsltProc = org.apache.xalan.xslt.XSLTProcessorFactory.getProcessor(</code><br/>
+ <p><code>org.apache.xalan.xslt.XSLTProcessor xsltProc = org.apache.xalan.xslt.XSLTProcessorFactory.getProcessor(</code><br/>
<code> new org.apache.xalan.xpath.xdom.XercesLiaison());</code></p>
<p>For more information, see <link idref="usagepatterns" anchor="dom-in">Processing DOM input and Producing DOM
output</link>.</p>
- <note>The DTM parser always attempts to expand entitity references in the source tree and stylesheet
+ <note>The DTM parser always attempts to expand eentityreferences in the source tree and stylesheet
tree. If you attempt to turn off entity reference expansion -- with DTMLiaison
- setShouldExpandEntitityRefs(false) -- DTMLaison does not make the setting and issues a message to that
- effect. If you want to turn off entity refereence expansion, instantiate the XSLTProcessor to use XercesLiaison and the
+ setShouldExpandEntitityRefs(false) -- DDTMLiaisondoes not make the setting and issues a message to that
+ effect. If you want to turn off entity rreferenceexpansion, instantiate the XSLTProcessor to use XercesLiaison and the
Xerces DOM parser.</note>
</s2>
</s1>
1.5.2.2 +4 -4 xml-xalan/xdocs/sources/xalan/extensions.xml
Index: extensions.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/extensions.xml,v
retrieving revision 1.5.2.1
retrieving revision 1.5.2.2
diff -u -r1.5.2.1 -r1.5.2.2
--- extensions.xml 2000/03/13 21:50:20 1.5.2.1
+++ extensions.xml 2000/03/16 18:50:09 1.5.2.2
@@ -5,7 +5,7 @@
*
-->
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
-
+
<s1 title="&xslt4j; Extensions">
<ul>
<li><link anchor="intro">Introduction</link></li>
@@ -23,7 +23,7 @@
<p><em>Extension elements</em> Unlike a literal result element, which the stylesheet simply transfers to the result tree, an extension element performs an action. For example, you can use the Redirect extension elements shipped with &xslt4j; to redirect portions of your transformation output to one or more files. Extension elements may contain attributes, text nodes, other elements, basically any valid XML. Extension elements may perform quite sophisticated actions, given that the extension routine (the implementation) has direct access to the XSL processor context object and to the element. In many cases the implementation returns void or null; if it does return a value, that value is placed in the transformation result tree.</p>
-<p><em>Extension functions</em>You can think of extension functions as extendint the core library of functions that XPath provides. An extension function passes arguments to the extension implementation and returns a value. You can use extension functions to return values that XSLT can interact with directly (node-set, result tree fragment, string, boolean, and number) as well as values (of any type) that you pass in turn to other extension functions.</p>
+<p><em>Extension functions</em>You can think of extension functions as extending the core library of functions that XPath provides. An extension function passes arguments to the extension implementation and returns a value. You can use extension functions to return values that XSLT can interact with directly (node-set, result tree fragment, string, boolean, and number) as well as values (of any type) that you pass in turn to other extension functions.</p>
</s2><anchor name="supported-lang"/>
<s2 title="Supported languages">
<p>&xslt4j; uses the <jump href="http://www.alphaworks.ibm.com/tech/bsf">Bean Scripting Framework (BSF)</jump>, an architecture for incorporating scripting into Java applications and applets. BSF allows an application to take advantage of scripting while being independent of any specific scripting language. To date, we have tested extensions implemented in Java and JavaScript. Other languages with BSF support appear in the table below.</p>
@@ -158,7 +158,7 @@
<li>The file name or URL for another document that contains the lxslt:component element.<br/>
Example: <code>xmlns:ext3="my-component.txt"</code></li>
</ul>
-<note>&xslt4j; identifies the URI by working through the list above. In other words, if the URI does not match an lxslt:comonent element prefix in the stylesheet, &xslt4j; attempts to map the URI to a fully qualified class name on the class path, and so on.</note>
+<note>&xslt4j; identifies the URI by working through the list above. In other words, if the URI does not match an lxslt:component element prefix in the stylesheet, &xslt4j; attempts to map the URI to a fully qualified class name on the class path, and so on.</note>
<p>If the stylesheet contains an lxslt:component element with a prefix attribute set to the extension prefix, the only function of the URI is to provide a unique namespace. If the stylesheet does not contain an lxslt:component, the URI must identify a Java class or a document containing the lxslt:component.</p>
</s3>
<s3 title="3. Designate the extension prefixes">
@@ -296,7 +296,7 @@
Testing Redirect extension:
<foobar-out>foo subelement text node</foobar-out>
</foo-out></source>
-<p>For more information on using the Redirect extension to send output to mulitple files, see <resource-ref idref="RedirectDoc"/>.</p>
+<p>For more information on using the Redirect extension to send output to multiple files, see <resource-ref idref="RedirectDoc"/>.</p>
</s3>
</s2><anchor name="ext-functions"/>
<s2 title="Using extension functions">
1.6.2.1 +29 -8 xml-xalan/xdocs/sources/xalan/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/faq.xml,v
retrieving revision 1.6
retrieving revision 1.6.2.1
diff -u -r1.6 -r1.6.2.1
--- faq.xml 2000/03/06 18:06:17 1.6
+++ faq.xml 2000/03/16 18:50:10 1.6.2.1
@@ -25,7 +25,7 @@
<q>Are there any shortcuts for using a transformation result as input for another transformation?</q>
- <a><p>You can always get a transformation result from the <resource-ref idref="XSLTOutputTargetDoc"/> object,
+ <a><p>You can always get a transformation result from the <resource-ref idref="XSLTResultTargetDoc"/> object,
and use it to set an <resource-ref idref="XSLTInputSourceDoc"/> object for another transformation, but yes, there is a
shortcut. Basically, you want to set up the XSLTResultTarget object
that receives the output from the first transformation (performed with the XML source, the first stylesheet, and the first
@@ -49,7 +49,7 @@
XSLTProcessor proc = XSLTProcessorFactory.getProcessor();
proc.process(new XSLTInputSource("foo.xml"),
new XSLTInputSource("foo.xsl"),
- new XSLTOutputTarget("foo.out");</source>
+ new XSLTResultTarget("foo.out");</source>
<p>Second scenario: you want to perform a number of transformations with the same stylesheet. To improve performance, you
compile the stylesheet once, and use the resulting <resource-ref idref="StylesheetRootDoc"/> object for each
transformation.</p>
@@ -84,12 +84,33 @@
<q>What can I do to speed up transformations?</q>
- <a><p>To be written.</p><ul>
- <li>Use the DTM liaison and XML parser.</li>
- <li>Use compiled stylesheets.</li>
- <li>Set the XSLTProcessor to function as a SAX DocumnetHandler, and respond to SAX events rather than waiting for
- the entire transformation to be completed.</li>
- <li>Set up your stylesheets to function efficiently.</li>
+ <a><p>In the ongoing development of &xslt4j;, enhancing performance is the primary goal of the &xslt4j; team.
+ Here are some preliminary
+ suggestions for you to keep in mind as you set up your applications:</p><ul>
+ <li>Use the default DTM liaison and XML parser unless you need to read or write a DOM. DOM is expensive in terms of memory,
+ and DOM and DOM2 do not include the interfaces required for optimal performance without the use of side
+ tables.<br/><br/></li>
+ <li>Set the XSLTProcessor to function as a SAX DocumentHandler, and respond to SAX events rather than waiting for
+ the entire transformation to be completed. The use of SAX allows incremental transformation and allows the XSLT
+ processor to create its own optimal tree (in place of a DOM).<br/><br/></li>
+ <li>Use compiled stylesheets for multiple transformations.<br/><br/></li>
+ <li>Set up your stylesheets to function efficiently.<br/><br/></li>
+ <ul>
+ <li>Don't use "//" (descendant axes) patterns near the root of a large document.<br/><br/></li>
+ <li>Use xsl:key elements and the key() function as an efficient way to retrieve node sets.<br/><br/></li>
+ <li>Where possible, use pattern matching rather than xsl:if or xsl:when statements.<br/><br/></li>
+ <li>xsl:for-each is fast because it does not require pattern matching.<br/><br/></li>
+ <li>Keep in mind that xsl:sort prevents incremental processing.<br/><br/></li>
+ <li>When you create variables, <xsl:variable name="fooElem" select="foo"/> is usually faster than
+ >xsl:variable name="fooElem"><xsl:value-of-select="foo"/></xsl:variable>.<br/><br/></li>
+ <li>Be careful using the last() function.<br/><br/></li>
+ <li>The use of index predicates within match patterns can be expensive.<br/><br/></li>
+ <li>Decoding and encoding is expensive.<br/><br/></li>
+ <li>The serializer must check each character for escaping; 30% to 60% or processing time is typically spent in
+ the serializer.</li>
+ </ul>
+ <li>For the ultimate in server-side scalability, perform transform operations on the client. For an example, see
+ <link idref="samples" anchor="appletxmltohtml">AppletXMLtoHTML</link>.</li>
</ul></a>
</faq>
1.6.2.2 +9 -6 xml-xalan/xdocs/sources/xalan/getstarted.xml
Index: getstarted.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/getstarted.xml,v
retrieving revision 1.6.2.1
retrieving revision 1.6.2.2
diff -u -r1.6.2.1 -r1.6.2.2
--- getstarted.xml 2000/03/13 21:50:21 1.6.2.1
+++ getstarted.xml 2000/03/16 18:50:10 1.6.2.2
@@ -1,6 +1,6 @@
<?xml version="1.0" standalone="no"?>
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
-
+
<s1 title="Getting Started">
<ul>
<li><link anchor="download">Downloading what you need</link></li>
@@ -17,7 +17,10 @@
<li>xalan.jar</li>
<li>xerces.jar</li>
</ul>
-<p>You can get the JDK or JRE from <jump href="http://www.ibm.com/java/jdk">ibm.com/java/jdk/</jump> or <jump href="http://www.java.sun.com">java.sun.com</jump>. Download the latest release of &xslt4j; and Xerces-java from <jump href="http://xml.apache.org/dist/">xml.apache.org</jump>. Check the <link idref="readme" anchor="status">version release notes</link> to verify that you are using the correct version of Xerces. <em>Important</em> You may experience unpredictable anomalies if your &xslt4j; and &xml4j; builds are not in synch. You can use &xslt4j; with other XML parsers, but it is up to you to implement liaisons to those parsers. Your liaison class should extend <resource-ref idref="XMLParserLiaisonDefaultDoc"/> and implement <resource-ref idref="XPathSupportDoc"/>.</p>
+<p>You can get the JDK or JRE from <jump href="http://www.ibm.com/java/jdk">ibm.com/java/jdk/</jump> or <jump href="http://www.java.sun.com">java.sun.com</jump>.</p>
+<p>Download <jump href="http://xml.apache.org/dist/xalan-j_1_0_0.jar">xalan-j_1_0_0.jar</jump> or <jump href="http://xml.apache.org/dist/xalan-j_1_0_0.tar.gz">xalan-j_1_0_0.tar.gz</jump>. Both of these files contain &xslt4j; 1.0.0 (with xalan.jar) and xerces.jar from Xerces-J 1.0.3. You can use the jar or tar utility to expand these files into a full build.</p>
+
+<note>You can use &xslt4j; with other XML parsers than the Xerces XML parser, but it is up to you to implement liaisons to those parsers. Your liaison class should extend <resource-ref idref="XMLParserLiaisonDefaultDoc"/> and implement <resource-ref idref="XPathSupportDoc"/>.</note>
<p>If you plan to run <link idref="extensions">XSLT extensions</link>. you need bsf.jar and bsfengines.jar, both of which are included in the &xslt4j; distribution. If you plan to run XSLT extensions implemented in JavaScript or another scripting language, you will need one or more additional files as indicated in <link idref="extensions" anchor="supported-lang">extensions language requirements</link>.</p>
</s2><anchor name="classpath"/>
@@ -41,12 +44,12 @@
<p>The extensions examples require additional JAR files on the class path, and the procedure for running the sample applet and sample servlet is different. For more information about all the samples, see <link idref="samples">&xslt4j; Samples</link>.</p>
</s2><anchor name="commandline"/>
<s2 title="Performing your own transformations from the command line">
-<p>java.org.apache.xalan.xslt.Process provides a basic utility for performing transformations from the command line. You use this utility, for example, to run the extensions samples. The command-line for most standard transformations is as follows:</p>
+<p>java.org.apache.xalan.xslt.Process provides a basic utility for performing transformations from the command line. You use this utility, for example, to run the extensions samples. The command line for most standard transformations is as follows:</p>
<p><code>java org.apache.xalan.xslt.Process -in <ref>xmlSource</ref></code><br/>
<code> -xsl <ref>stylesheet</ref> -out <ref>outputfile</ref></code></p>
<p>where <ref>xmlSource</ref> is the XML source file name, <ref>stylesheet</ref> is the XSL stylesheet file name, and <ref>outputfile</ref> is the output file name.</p>
<p>If you want the output to be displayed on the screen, simply omit the -out flag and argument.</p>
-<p>You can use this utility to try out XSL stylesheets you have written, to make sure they do what you expect with the XML source files they are designed to transform. The utility provides useful messages if the source file or stylesheet is not well-formed. If you include a DOCTYPE statement in your XML source files and include the -validate flag on the command line, the utility will also let you know whether the XML document is valid (conforms to that DOCTYPE). For more information, see <link idref="commandline">Command-Line Utility</link>.</p>
+<p>You can use this utility to try out XSL stylesheets you have written, to make sure they do what you expect with the XML source files they are designed to transform. The utility provides useful messages if the source file or stylesheet is not well formed. If you include a DOCTYPE statement in your XML source files and include the -validate flag on the command line, the utility will also let you know whether the XML document is valid (conforms to that DOCTYPE). For more information, see <link idref="commandline">Command-Line Utility</link>.</p>
</s2><anchor name="java-apps"/>
<s2 title="Setting up your own Java applications">
<p>You can start by using your own XML source files and XSL stylesheets with the sample applications, which illustrate a number of the <link anchor="usage-patterns">basic usage patterns</link>.</p>
@@ -57,10 +60,10 @@
If the XML document contains a stylesheet Processing Instruction (PI), you do not need to create a separate
XSLTInputSource object for an XSL stylesheet.<br/><br/></li>
<li>For improved performance with a series of transformations, use the <resource-ref idref="XSLTProcessorProcessStylesheetDoc"/> to compile the XSL stylesheet (the result is a <resource-ref idref="StylesheetRootDoc"/>), and then use the <resource-ref idref="StylesheetRootProcessDoc"/> to perform the transformations.<br/><br/>
-Compiling the stylesheet is also useful when you need to get information from the stylesheet before the tranformation occurs, for
+Compiling the stylesheet is also useful when you need to get information from the stylesheet before the transformation occurs, for
instance, when you need to find out the output encoding in order to construct the right kind of Writer.
You must also compile the stylesheet if you are using the XSLTProcessor as a SAX document handler (see <link idref="usagepatterns" anchor="sax">Generating and responding to SAX events</link>).<br/><br/></li>
-<li>Set up an <resource-ref idref="XSLTResultTargetDoc"/> for the transformation output. You can use a file name or URL, character stream, byte stream, or SAX document handler to instantiate an XSLTOutputTarget object.<br/><br/></li>
+<li>Set up an <resource-ref idref="XSLTResultTargetDoc"/> for the transformation output. You can use a file name or URL, character stream, byte stream, or SAX document handler to instantiate an XSLTResultTarget object.<br/><br/></li>
<li>Use the XSLTProcessor process() method to perform the transformation, or the StylesheetRoot process() method to perform a series of transformations with the same stylesheet.<br/><br/>
XSLTProcessor is thread-safe for one instance per thread. If you are using the same instance of XSLTProcessor to perform
more than one transformation, call the reset method between transformations. StylesheetRoot is multithread-safe, and a single instance may be used across threads. Accordingly, you can call a StylesheetRoot object process() method repeatedly without resetting the StyleSheetRoot.</li>
1.6.2.1 +2 -2 xml-xalan/xdocs/sources/xalan/javadocOverview.xml
Index: javadocOverview.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/javadocOverview.xml,v
retrieving revision 1.6
retrieving revision 1.6.2.1
diff -u -r1.6 -r1.6.2.1
--- javadocOverview.xml 2000/03/06 13:31:48 1.6
+++ javadocOverview.xml 2000/03/16 18:50:11 1.6.2.1
@@ -86,10 +86,10 @@
processStylesheet method to compile the XSL stylesheet. The result is a
{@link org.apache.xalan.xslt.StylesheetRoot} object with its own process() method for performing transformations.
Compiling the stylesheet is also useful when you need to get information from the
- stylesheet before the tranformation occurs. You also must compile the stylesheet if you are using the
+ stylesheet before the transformation occurs. You also must compile the stylesheet if you are using the
XSLTProcessor as a SAX document handler.<br/><br/></li>
<li>Set up an {@link org.apache.xalan.xslt.XSLTResultTarget} for the transformation output. You can use a
- file name or URL, character stream, byte stream, or SAX document handler to instantiate an XSLTOutputTarget
+ file name or URL, character stream, byte stream, or SAX document handler to instantiate an XSLTResultTarget
object.<br/><br/></li>
<li>Use the XSLTProcessor or (if you have compiled the stylesheet) the(@link org.apache.xalan.xslt.StylesheetRoot}
process method to perform the transformation.<br/><br/>
1.4.2.1 +3 -3 xml-xalan/xdocs/sources/xalan/org-apache-xalan-xpath-dtm.xml
Index: org-apache-xalan-xpath-dtm.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/org-apache-xalan-xpath-dtm.xml,v
retrieving revision 1.4
retrieving revision 1.4.2.1
diff -u -r1.4 -r1.4.2.1
--- org-apache-xalan-xpath-dtm.xml 2000/03/06 13:31:48 1.4
+++ org-apache-xalan-xpath-dtm.xml 2000/03/16 18:50:11 1.4.2.1
@@ -65,7 +65,7 @@
<p>DOM (Document Object Model) is a standard interface for interacting with XML documents. &xslt4j; fully
supports this interface. For large XML documents, however, this may involve considerable overhead, since &xslt4j;
must create one or more Java objects for each Node in the document.</p>
- <p>For the majority of cases -- your input and output are URLS, files, or streams, and you use the default Liaison
+ <p>For the majority of cases -- your input and output are URLs, files, or streams, and you use the default Liaison
{@link org.apache.xalan.xpath.dtm.DTMLiaison} and XML parser {@link org.apache.xalan.xpath.dtm.DTM} -- &xslt4j; avoids
this overhead by implementing the Document Table Model (DTM), a pseudo-DOM that uses integer arrays in place of the DOM.
For larger input and output trees, the performance improvements can be very significant.</p>
@@ -77,8 +77,8 @@
</code></p>
<p>When your provide input or write output in the form of a DOM Node, the XSLTProcessor switches to
{@link org.apache.xalan.xpath.xdom.XercesLiaison} and the Xerces DOM parser. You can explicitly instantiate an
- XSLTProcesssor to use XercesLiaison and the Xerces DOM parser as follows:</p>
- <p><code>org.apache.xalan.xsltXSLT.Processor xsltProc = org.apache.xalan.xslt.XSLTProcessorFactory.getProcessor(</code><br/>
+ XSLTProcessor to use XercesLiaison and the Xerces DOM parser as follows:</p>
+ <p><code>org.apache.xalan.xslt.XSLTProcessor xsltProc = org.apache.xalan.xslt.XSLTProcessorFactory.getProcessor(</code><br/>
<code> new org.apache.xalan.xpath.xdom.XercesLiaison());</code></p>
</s2>
</s1>
1.5.2.1 +16 -12 xml-xalan/xdocs/sources/xalan/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/readme.xml,v
retrieving revision 1.5
retrieving revision 1.5.2.1
diff -u -r1.5 -r1.5.2.1
--- readme.xml 2000/03/06 17:32:47 1.5
+++ readme.xml 2000/03/16 18:50:11 1.5.2.1
@@ -95,7 +95,7 @@
If you are running Windows 95/98/NT, you can use the Cygwin port of GNU. Be sure to put the
appropriate Cygwin bin directory at the beginning of your system path. For information about
Cygwin, see <jump href="http://www.sourceware.cygnus.com/cygwin/">Cygwin</jump>.<br/><br/></li>
- <li>Place <resource-ref idref="xerces-used"/> xerces.jar in the Java classpath.<br/><br/></li>
+ <li>Place <resource-ref idref="xerces-used"/> xerces.jar in the Java class path.<br/><br/></li>
<li>If you are working in Windows, set MAKE_MODE as follows:<br/><br/>
<code>set MAKE_MODE=UNIX</code><br/><br/></li>
<li>Run the make file in the &xslt4j; root directory:<br/><br/>
@@ -104,12 +104,13 @@
<p>If you want to do the build without the GNU build environment, keep the following in mind:</p>
<ul>
<li>Set the class path to include the src directory, xerces.jar, bsf.jar, and bsfengines.jar.</li>
- <li>Use javac to compile all the .java files in the src tree. </li>
+ <li>Use a Java compiler (such as the IBM Just-In-Time compiler or the Sun javac) to compile all the .java files in the src
+ tree. </li>
<li>Use the Sun jar utility to store the resulting .class files in xalan.jar</li>
</ul>
</s3><anchor name="samples"/>
<s3 title="Rebuilding a sample application">
- <p>If you modify a sample and want to recompile it, you can run javac in the directory containing the
+ <p>If you modify a sample and want to recompile it, you can run the Java compiler in the directory containing the
example. Be sure xalan.jar and xerces.jar are on the class path. To recompile (and run!) the class files in the
Servlet subdirectory, the javax.servlet and javax.servlet.http packages must also be on the class path. Sun
distributes these packages in the JSWDK 1.0.1 servlet.jar file.</p>
@@ -120,13 +121,14 @@
<p>&xslt4j; includes a number of XML source files, XSL stylesheets, document type definition (DTD)
files, entity relationship (ENT) files, graphics, and a JavaScript file that provide the input for the Xalan
HTML User's Guide, and the overview and package-level documents used during the generation of Javadoc.</p>
- <p>To rebuild the documentation, you must use the JDK 1.2.2 java and javadoc tools. If the JDK 1.2.2 bin and lib
- directories are not on your class path, you can edit the make.include file in the Xalan root directory so the make file
- can find the JDK 1.2.2 java and javadoc tools. You can also include java and javadoc arguments on the make file command
- line. See the make.include file for the details.</p>
-
+ <p>To rebuild the documentation, you must use a Stylebook tool from xml.apache.org and the JDK 1.2.2 java and javadoc
+ tools. Stylebook (which uses Xalan and Xerces) and the required document definition files, stylesheets, and resources
+ are stored in xml-site-style.tar.gz, and are unzipped when you run the make files as described below. If the JDK 1.2.2 bin
+ and lib directories are not on your class path, you can edit the make.include file in the Xalan root directory so the make
+ file can find the JDK 1.2.2 java and javadoc tools. You can also include java and javadoc arguments on the make file
+ command line. See the make.include file for the details.</p>
<p>To generate the Xalan HTML User's Guide, run the Xalan make file in the Xalan xdocs directory:<br/><br/>
- <code>make stylebook</code></p>
+ <code>make makesbook</code></p>
<p>To generate Xalan API documentation, set up the make file to use the Javadoc tool in the Java JDK 1.2.2 bin
directory.</p>
<p>Do the following:</p>
@@ -134,15 +136,17 @@
<li>Put the Java JDK 1.2.2 bin directory on your path (in front of any JDK 1.1.x bin
directory that appears on the path).<br/><br/></li>
<li>In the Xalan docs directory, run the Xalan make file as follows:<br/><br/>
- <code>make javadoc</code><br/><br/></li>
+ <code>make makejavadoc</code><br/><br/></li>
</ol>
<p>If you want to rebuild the documentation without using the GNU build environment, keep the following in
mind:</p>
<ul>
+ <li>Unzip xml-site-style.tar.gz into the xdocs directory (the operation creates a number of subdirectories).
+ <br/><br/></li>
<li>Be sure stylebook-1.0-b2.jar, xalanjdoc.jar, xalan.jar, bsf.jar, bsfengines.jar, and xerces.jar are on the class
path.<br/><br/></li>
<li>To build doc in a build/docs subdirectory, run StyleBook from the xdocs directory as follows:<br/><br/>
-<code>java org.apache.stylebook.StyleBook "targetDirectory=../build/docs/" sources/xalanLocal.xml style</code>
+ <code>java org.apache.stylebook.StyleBook "targetDirectory=../build/docs/" sources/xalanLocal.xml style</code>
<br/><br/></li>
<li>To build the HTML source files that javadoc needs for top-level and package-level documentation, run
StyleBook from the xdocs directory as follows:<br/><br/>
@@ -150,7 +154,7 @@
<li>Before you run javadoc, make sure the following directory structure exists under the Xalan root
directory: build/docs/apidocs.<br/><br/></li>
<li>To build the API documentation, run the JDK 1.2.2 javadoc tool from the xdocs directory:<br/><br/>
-<code>-doclet xalanjdoc.Standard -public -overview ../src/javadocOverview.html -sourcepath ../src -group "XSLT Packages" "org.apache.xalan.xslt*" -group "XPath Packages" "org.apache.xalan.xpath*" org.apache.xalan.xpath org.apache.xalan.xpath.xdom org.apache.xalan.xpath.dtm org.apache.xalan.xpath.xml org.apache.xalan.xslt org.apache.xalan.xslt.trace org.apache.xalan.xslt.client org.apache.xalan.xslt.extensions -windowtitle Xalan -d ../build/docs/apidocs
+<code>-doclet xalanjdoc.Standard -public -overview ../src/javadocOverview.html -sourcepath ../src -group XSLT_Packages "org.apache.xalan.xslt*" -group XPath_Packages "org.apache.xalan.xpath*" org.apache.xalan.xpath org.apache.xalan.xpath.xdom org.apache.xalan.xpath.dtm org.apache.xalan.xpath.xml org.apache.xalan.xslt org.apache.xalan.xslt.trace org.apache.xalan.xslt.client org.apache.xalan.xslt.extensions -windowtitle Xalan -d ../build/docs/apidocs
</code></li>
</ul>
</s3>
1.7.2.1 +4 -3 xml-xalan/xdocs/sources/xalan/resources.xml
Index: resources.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/resources.xml,v
retrieving revision 1.7
retrieving revision 1.7.2.1
diff -u -r1.7 -r1.7.2.1
--- resources.xml 2000/03/06 13:31:48 1.7
+++ resources.xml 2000/03/16 18:50:11 1.7.2.1
@@ -61,9 +61,10 @@
<human-resource id="xalandev" name="Xalan Development Mailing List" mailto="xalan-dev@xml.apache.org"/>
<human-resource id="sboag" name="Scott Boag" mailto="scott_boag@lotus.com"/>
- <human-resource id="dnbertoni" name="David N. Bertoni" mailto="david_n_bertoni@lotus.com"/>
- <human-resource id="rweir" name="Robert Weir" mailto="robert_weir@lotus.com"/>
- <human-resource id="dleslie" name="Don Leslie" mailto="donald_leslie@lotus.com"/>
+ <human-resource id="dnbertoni" name="David N. Bertoni" mailto="david_n_bertoni@lotus.com"/>
+ <human-resource id="rweir" name="Robert Weir" mailto="robert_weir@lotus.com"/>
+ <human-resource id="scurcuru" name="Shane Curcuru" mailto="shane_curcuru@lotus.com"/>
+ <human-resource id="dleslie" name="Don Leslie" mailto="donald_leslie@lotus.com"/>
<human-resource id="pdick" name="Paul Dick" mailto="paul_dick@lotus.com"/>
<human-resource id="dburson" name="Dean Burson" mailto="dean_burson@lotus.com"/>
<human-resource id="nmendelsohn" name="Noah Mendelsohn" mailto="noah_mendelsohn@lotus.com"/>
1.8.2.2 +55 -4 xml-xalan/xdocs/sources/xalan/samples.xml
Index: samples.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/samples.xml,v
retrieving revision 1.8.2.1
retrieving revision 1.8.2.2
diff -u -r1.8.2.1 -r1.8.2.2
--- samples.xml 2000/03/13 21:50:21 1.8.2.1
+++ samples.xml 2000/03/16 18:50:12 1.8.2.2
@@ -1,9 +1,60 @@
<?xml version="1.0" standalone="no"?>
<!--
- * Copyright (c) 1999 Lotus Development Corporation, Inc. All Rights Reserved.
- * This software is provided without a warranty of any kind.
+ * The Apache Software License, Version 1.1
*
--->
+ *
+ * Copyright (c) 1999 The Apache Software Foundation. All rights
+ * reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright
+ * notice, this list of conditions and the following disclaimer.
+ *
+ * 2. Redistributions in binary form must reproduce the above copyright
+ * notice, this list of conditions and the following disclaimer in
+ * the documentation and/or other materials provided with the
+ * distribution.
+ *
+ * 3. The end-user documentation included with the redistribution,
+ * if any, must include the following acknowledgment:
+ * "This product includes software developed by the
+ * Apache Software Foundation (http://www.apache.org/)."
+ * Alternately, this acknowledgment may appear in the software itself,
+ * if and wherever such third-party acknowledgments normally appear.
+ *
+ * 4. The names "Xalan" and "Apache Software Foundation" must
+ * not be used to endorse or promote products derived from this
+ * software without prior written permission. For written
+ * permission, please contact apache@apache.org.
+ *
+ * 5. Products derived from this software may not be called "Apache",
+ * nor may "Apache" appear in their name, without prior written
+ * permission of the Apache Software Foundation.
+ *
+ * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+ * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+ * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
+ * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+ * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
+ * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ * ====================================================================
+ *
+ * This software consists of voluntary contributions made by many
+ * individuals on behalf of the Apache Software Foundation and was
+ * originally based on software copyright (c) 1999, Lotus
+ * Development Corporation., http://www.lotus.com. For more
+ * information on the Apache Software Foundation, please see
+ * <http://www.apache.org/>.
+ -->
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
<s1 title="Samples">
@@ -64,7 +115,7 @@
<p>where <ref>param</ref> is the stylesheet parameter (a string of your choice).</p>
</s2><anchor name="xpath"/>
<s2 title="ApplyXPath">
- <p>What it does: The ApplyXPath class uses the XPathAPi class to execute an XPath expression against an XML document
+ <p>What it does: The ApplyXPath class uses the XPathAPI to execute an XPath expression against an XML document
and returns the nodes (if any) it finds. XPathAPI contains some convenience methods for using XPath expressions to return
single Nodes, NodeLists, and XObjects. In the future, we plan to incorporate user feedback and move these methods into the
core API.</p>
1.6.2.1 +7 -7 xml-xalan/xdocs/sources/xalan/usagepatterns.xml
Index: usagepatterns.xml
===================================================================
RCS file: /home/cvs/xml-xalan/xdocs/sources/xalan/usagepatterns.xml,v
retrieving revision 1.6
retrieving revision 1.6.2.1
diff -u -r1.6 -r1.6.2.1
--- usagepatterns.xml 2000/03/06 13:31:48 1.6
+++ usagepatterns.xml 2000/03/16 18:50:12 1.6.2.1
@@ -114,7 +114,7 @@
<source>import org.apache.xalan.xslt.*;
...
java.io.OutputStream byteStream = new java.io.ByteArrayOutputStream();
-XSLTRegultTarget out = new XSLTResultTarget(byteStream)
+XSLTResultTarget out = new XSLTResultTarget(byteStream)
// Do the transformation...
// Work with the OutputStream...</source>
@@ -124,11 +124,11 @@
<p>To set a stylesheet parameter, use the XSLTProcessor setStylesheetParam(String key, String expression) method, where key is the parameter name and expression is an XPath expression. If the parameter is a String, enclose it in single quotes to make it a String expression.</p>
<p>You can also use setStylesheetParam(String key, XObject value). This option is useful when you are working with the XPath API. For example, you could use the XObject returned by an Xpath function to set a parameter.</p>
<p>From the <link idref="commandline">command line</link>, include a -param argument. For example:</p>
-<p><code>java org.apache.xalan.xsltProcess -in foo.xml -xsl foo.xsl -param 'boo'</code></p>
+<p><code>java org.apache.xalan.xslt.Process -in foo.xml -xsl foo.xsl -param 'boo'</code></p>
</s2><anchor name="compiled"/>
<s2 title="Compiling stylesheets">
-<p>A <resource-ref idref="StylesheetRootDoc"/> object is a binary representation of a stylesheet that adds efficiency to the performance of repeated transformations and supports threadsafe concurrent access by multiple clients. If, for example, you are setting up a servlet to perform transformations, you can improve performance by compiling any stylesheets the servlet repeatedly uses.</p>
-<p>To compile a stylesheet, use one of the the <resource-ref idref="XSLTProcessorDoc"/> processStylesheet methods. This operation also sets the XSLTProcessor Stylesheet property. In the interest of clarity, you may want to explicitly set that property. When you call the process method, include a null for the "uncompiled" stylesheet parameter so XLTProcessor uses the compiled stylesheet. For example:</p>
+<p>A <resource-ref idref="StylesheetRootDoc"/> object is a binary representation of a stylesheet that adds efficiency to the performance of repeated transformations and supports thread-safe concurrent access by multiple clients. If, for example, you are setting up a servlet to perform transformations, you can improve performance by compiling any stylesheets the servlet repeatedly uses.</p>
+<p>To compile a stylesheet, use one of the the <resource-ref idref="XSLTProcessorDoc"/> processStylesheet methods. This operation also sets the XSLTProcessor Stylesheet property. In the interest of clarity, you may want to explicitly set that property. When you call the process method, include a null for the "uncompiled" stylesheet parameter so XSLTProcessor uses the compiled stylesheet. For example:</p>
<source>import org.apache.xalan.xslt.*;
...
XSLTProcessor processor = XSLTProcessorFactory.getProcessor();
@@ -138,14 +138,14 @@
...
processor.process(new XSLTInputSource("foo.xml"),
null, // Use the Stylesheet property setting.
- new XSLTOutputTarget("foo.out"));</source>
+ new XSLTResultTarget("foo.out"));</source>
<p>Alternative: StylesheetRoot has its own process method, so another way to do the preceding is as follows:</p>
<source>import org.apache.xalan.xslt.*;
..
XSLTProcessor processor = XSLTProcessorFactory.getProcessor();
StylesheetRoot style = processor.processStylesheet(new XSLTInputSource("foo.xsl"));
...
-style.process(new XSLTInputSource("foo.xml"), new XSLTOutputTarget("foo.out"));</source>
+style.process(new XSLTInputSource("foo.xml"), new XSLTResultTarget("foo.out"));</source>
<p>You should use the StylesheetRoot process() method if you are using a StylesheetRoot object to transform multiple XML sources.</p>
<p>If you want to use the XSLTProcessor as a SAX document handler, you must provide the processor a compiled stylesheet. See <link anchor="sax">Generating and Responding to SAX events</link>.</p>
</s2><anchor name="dom-in"/>
@@ -264,7 +264,7 @@
<p>For a more compact (and elegant) form of this example, see the <link idref="samples" anchor="pipe">Pipe</link>. For an example that uses SAX DocumentHandlers and the Xerces SAX parser to parse the XML input and XSL stylesheet and produce the transformation result, see the <link idref="samples" anchor="sax">PureSAX</link>.</p>
</s2><anchor name="xpath"/>
<s2 title="Working with XPath expressions">
-<p>XSL stylesheets use XPath expressions to select nodes, specify conditions, and generate text for the result tree. XPath provides an API that you can call directly. For example, you may want to select nodes programatically and do your own processing without a stylesheet.</p>
+<p>XSL stylesheets use XPath expressions to select nodes, specify conditions, and generate text for the result tree. XPath provides an API that you can call directly. For example, you may want to select nodes programmatically and do your own processing without a stylesheet.</p>
<p>The XPathAPI class, in the samples/ApplyXPath subdirectory, contains several convenience methods that you can use to return single DOM Nodes, NodeLists, and XObjects. In the future, we plan to incorporate user feedback and move these methods into the core API.</p>
<p>If you are interested in the API for executing XPath expressions, we suggest you take a look at the methods in XPathAPI,
and send us feedback on what best meets your needs.</p>