| <s3 title="Changes for &xslt4j; 2.2.D9"> |
| <p> Core (Non-XSLTC) source code updates:</p> |
| <ul><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/res XSLTInfo.properties<br/><ref>Committer's log entry: </ref>2.2.D8<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor XSLProcessorVersion.java<br/><ref>Committer's log entry: </ref>2.2.D8<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer NodeSortKey.java<br/><ref>Committer's log entry: </ref>Submitted fix for http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2851.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/xslt Process.java<br/><ref>Committer's log entry: </ref>Just added some stuff to diagnose bugs for flavor th.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes WalkerFactory.java |
| java/src/org/apache/xpath/compiler Compiler.java |
| java/src/org/apache/xpath/patterns |
| ContextMatchStepPattern.java StepPattern.java<br/><ref>Committer's log entry: </ref>These are changes submitted (offline) by Mukund Raghavachari/Watson/IBM@IBMUS. |
| |
| This fixes a bug with match="chapter//footnote[1]" patterns. |
| |
| The main change here is minor to remove the automatic attachment of parent::* |
| to simple step patterns. |
| |
| He has re-implemented executePredicates to be |
| more efficient. Given a pattern such as row[6], it |
| does not iterate over the entire axis until it reaches |
| the node to see if it is the sixth node. Rather, |
| starting from the current node, it works backwards |
| (preceding siblings) until it either runs out of nodes |
| or finds more than six nodes that match the |
| predicate [I can explain it better if desired]. |
| This optimization improves performance slightly |
| overall. It helps decoy and patterns most (by |
| about 10%). |
| |
| The other optimization that I implemented was the |
| following. For a pattern foo[][3][][4] ..., where more |
| than one predicate is a number (position check), |
| in checking the predicate [4], the fact that the |
| current node has passed foo[][3] implies that it is |
| the only node that is the third node among its |
| siblings that passes foo[]. Therefore, any |
| subsequent position checks can be true if and |
| only if the position is [1]. This optimization is not |
| used by the xsltmark benchmarks and so does |
| not offer any performance benefits.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes DescendantIterator.java<br/><ref>Committer's log entry: </ref>Fix for http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1336<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/compiler Lexer.java<br/><ref>Committer's log entry: </ref>Resize the m_patternMap if m_patternMapSize exceeds the bounds.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/extensions |
| ExtensionHandlerGeneral.java |
| ExtensionHandlerJavaPackage.java |
| ExtensionsTable.java MethodResolver.java |
| java/src/org/apache/xalan/lib Extensions.java |
| java/src/org/apache/xalan/lib/sql ConnectionPoolManager.java |
| java/src/org/apache/xalan/processor ProcessorLRE.java |
| ProcessorTemplateElem.java StylesheetHandler.java |
| TransformerFactoryImpl.java XSLTAttributeDef.java |
| XSLTElementProcessor.java |
| java/src/org/apache/xalan/res XSLTErrorResources.java |
| java/src/org/apache/xalan/serialize CharInfo.java |
| WriterToUTF8Buffered.java |
| java/src/org/apache/xalan/templates ElemExtensionCall.java |
| ElemExtensionDecl.java ElemMessage.java |
| FuncDocument.java FuncFormatNumb.java |
| OutputProperties.java StylesheetRoot.java |
| java/src/org/apache/xalan/transformer TrAXFilter.java |
| TransformerHandlerImpl.java |
| TransformerIdentityImpl.java TransformerImpl.java |
| java/src/org/apache/xalan/xslt Process.java |
| java/src/org/apache/xml/dtm DTMException.java |
| DTMManager.java |
| java/src/org/apache/xml/dtm/ref ChunkedIntArray.java |
| CoroutineManager.java CoroutineSAXParser.java |
| CoroutineSAXParser_Xerces.java DTMBuilder.java |
| DTMDefaultBase.java DTMDefaultBaseIterators.java |
| DTMDefaultBaseTraversers.java |
| DTMManagerDefault.java |
| IncrementalSAXSource_Filter.java |
| IncrementalSAXSource_Xerces.java |
| java/src/org/apache/xml/dtm/ref/sax2dtm SAX2DTM.java |
| java/src/org/apache/xml/utils ObjectPool.java QName.java |
| URI.java |
| java/src/org/apache/xpath NodeSet.java NodeSetDTM.java |
| VariableStack.java XPath.java XPathContext.java |
| java/src/org/apache/xpath/axes WalkerFactory.java |
| java/src/org/apache/xpath/functions FuncSubstring.java |
| FunctionDef1Arg.java |
| java/src/org/apache/xpath/objects |
| XRTreeFragSelectWrapper.java XStringForChars.java |
| java/src/org/apache/xpath/operations Variable.java |
| java/src/org/apache/xpath/res XPATHErrorResources.java<br/><ref>Committer's log entry: </ref>Getting all (almost all) error message strings into the resource bundle<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>07/27/2001<br/><ref>Removed: </ref>java/src/org/apache/xml/dtm/ref DTMBuilder.java<br/><ref>Committer's log entry: </ref>Accidentally added. Now deleting.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath Expression.java |
| java/src/org/apache/xpath/axes AxesWalker.java |
| LocPathIterator.java PredicatedNodeTest.java |
| ReverseAxesWalker.java |
| java/src/org/apache/xpath/objects XNumber.java |
| java/src/org/apache/xpath/operations Variable.java<br/><ref>Committer's log entry: </ref>If a proximity predicate is a stable number (variable or number literal) then, |
| once the node is found, don't keep searching! (since only one |
| node is possible).<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/30/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref DTMDefaultBase.java<br/><ref>Committer's log entry: </ref>In getNextNamespaceNode and getFirstNamespaceNode, was |
| sometimes returning a node without the DTM identity bits. |
| Fix for http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2878.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/30/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/compiler OpMap.java<br/><ref>Committer's log entry: </ref>Throw real error instead of runtime error in getFirstPredicateOpPos |
| for better error reporting.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/30/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes PredicatedNodeTest.java |
| java/src/org/apache/xpath/compiler OpMap.java<br/><ref>Committer's log entry: </ref>Bit of a hack to make /descendant-or-self::north with getFirstPredicateOpPos |
| where getFirstPredicateOpPos was always throwing an error if |
| there was not a predicate (!! Should have been discovered before |
| now?!?!). If -2 return -2 (instead of throwing an error), and |
| handle this case in PredicatedNodeTest#initPredicateInfo.<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/30/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql ObjectArray.java |
| SQLDocument.java SQLErrorDocument.java |
| XConnection.java<br/><ref>Committer's log entry: </ref>Added the original pquery and streaming mode functionality |
| Submitted by: John Gentilin<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/30/2001<br/><ref>Added: </ref>java/src/org/apache/xalan/lib/sql DTMDocument.java<br/><ref>Committer's log entry: </ref>Added DTM Document, a common impl between SQLDocument and SQLErrorDocument |
| Submitted by: John Gentilin<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/30/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes DescendantIterator.java |
| WalkerFactory.java<br/><ref>Committer's log entry: </ref>Fix addresses http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=XalanJ2, |
| and a whole class of related problems.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/31/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/objects XNodeSet.java XObject.java |
| java/src/org/apache/xpath/patterns StepPattern.java<br/><ref>Committer's log entry: </ref>Detach expressions in match patterns. Also, defined |
| numWithSideEffects and boolWithSideEffects (for lack of |
| better names) that will increment the iterator, and call these |
| for predicates. The combination of these results in about an |
| 18% performance improvement for decoy.xsl. |
| Credits to Mukund Raghavachari/Watson/IBM@IBMUS.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>07/31/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/extensions |
| ExtensionHandlerGeneral.java |
| java/src/org/apache/xalan/res XSLTErrorResources.java |
| java/src/org/apache/xalan/templates ElemExtensionDecl.java<br/><ref>Committer's log entry: </ref>Add support for external scripts (ie, the src attribute on a script element)<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/31/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath XPathContext.java |
| java/src/org/apache/xpath/axes ChildTestIterator.java |
| OneStepIteratorForward.java<br/><ref>Committer's log entry: </ref>In XPathContext#createDTMIterator(int node), call |
| OneStepIteratorForward(Axis.SELF) |
| instead of DescendantIterator. This addresses one of the bugs |
| in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2925 |
| (i.e. <xsl:copy-of select="xalan:nodeset($stylesheets)"/>... |
| The DescendantIterator was enumerating all of the nodes in the RTF |
| rather than just the one.)<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/31/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql ConnectionPool.java |
| ConnectionPoolManager.java DTMDocument.java |
| DefaultConnectionPool.java ObjectArray.java |
| PooledConnection.java SQLDocument.java |
| SQLErrorDocument.java XConnection.java<br/><ref>Committer's log entry: </ref>Added Error Managment and javadocs |
| Submitted by: John Gentilin<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/01/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/patterns StepPattern.java<br/><ref>Committer's log entry: </ref>Fixed some major problems with position() and last() in secondary |
| predicates for match patterns. Credit goes to |
| Mukund Raghavachari/Watson/IBM@IBMUS for flagging these.<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>08/01/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql XConnection.java<br/><ref>Committer's log entry: </ref>Update after building Unit Test's |
| Submitted by: John Gentilin<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>08/01/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor XSLTAttributeDef.java<br/><ref>Committer's log entry: </ref>Fix for Bugzilla 2930. Fix from Alexander Rudnev. Handle namespaced elements.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/01/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm DTMAxisIterator.java |
| java/src/org/apache/xml/dtm/ref DTMAxisIteratorBase.java |
| DTMDefaultBaseIterators.java |
| java/src/org/apache/xpath/axes OneStepIterator.java<br/><ref>Committer's log entry: </ref>Addresses http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2945 |
| |
| Bug was caused by (redundent) cloneWithReset being called from |
| the UnionPathIterator, and the iterator in OneStepIterator not being |
| reset. (Need to review: check other iterators for this.) |
| |
| Call reset on the iterator in OneStepIterator#reset. Reset the position |
| value in the ancestor iterator reset. Define DTMAxisIterator#cloneIterator |
| to not reset the iterator position, and fix the implementations of |
| this to not call clone.reset().<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/02/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java |
| java/src/org/apache/xpath NodeSetDTM.java |
| java/src/org/apache/xpath/functions FuncExtFunction.java |
| java/src/org/apache/xpath/objects XBoolean.java |
| XNodeSet.java XNumber.java XObject.java<br/><ref>Added: </ref>java/src/org/apache/xpath/objects XNodeSetForDOM.java<br/><ref>Committer's log entry: </ref>Address http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2925 |
| |
| Create new XObject, XNodeSetForDOM, which is constructed |
| from a Node, NodeList, or NodeIterator, and acts the same as |
| XNodeSet, except it returns the original object for object(), |
| nodeset(), and nodelist(). |
| |
| Add XObject#create(Object val, XPathContext xctxt), which is |
| called from TransformerImpl#setParameter(s), and |
| FuncExtFunction#execute (for the return values of the |
| extension). |
| |
| XBoolean and XNumber now also have Boolean and Number |
| constructors, in which case the original object will also be |
| returned from the object() method. |
| |
| This should make the conversion from java object to XObject |
| consistent between function returns and setParameter. These |
| changes should also fix a bug where NodeLists weren't being converted.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>08/03/2001<br/><ref>Added: </ref>java/src/org/apache/xml/utils NamespaceSupport2.java<br/><ref>Committer's log entry: </ref>Replacement for org.xml.sax.helpers.NamespaceSupport; extends |
| that API so it can be easily swapped in. |
| |
| Current changes; |
| |
| Minor code reorg. I'm sorry, but I find classes easier to read |
| if fields are defined before methods reference them rather than |
| at end, especially when inner classes are present. |
| |
| Punt stack vector in favor of doubly-linked list. (It was already |
| singly-linked in parallel with the vector!) |
| |
| The whole dirty-tables concept was broken, because Context's |
| ctor always called copyTables and thus always marked tables |
| dirty. It also wasted some time setting itself only to be reset by |
| setParent. I've fixed both by parameterizing the ctor and making |
| copyTables specific to prep-for-new-declaration. (Could be |
| moved back into the declaration method, for that matter.) |
| |
| I'm dubious about the caches in processName. As far as I can |
| tell, Xalan per se never actually uses that method... |
| |
| The use of Hashtables is questionable. Hashtable is |
| known to be inefficient and oversynchronized in older JVMs, and |
| the fact that this is a bidirectional mapping suggests that an |
| approach similar to our own String Pool -- lighter-weight, more |
| targeted, hashing without reduplicating the two column tables -- |
| would be a win. Since these are typically short sets, even |
| simple linear search is worth considering!<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>08/03/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor StylesheetHandler.java |
| java/src/org/apache/xalan/templates ElemTemplateElement.java |
| java/src/org/apache/xalan/transformer ResultTreeHandler.java |
| TransformSnapshotImpl.java<br/><ref>Committer's log entry: </ref>Cutover to NamespaceSupport2, q.v.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>08/03/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils NamespaceSupport2.java<br/><ref>Committer's log entry: </ref>Continuing code review.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>08/03/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils NamespaceSupport2.java<br/><ref>Committer's log entry: </ref>More efficient prefixes-for-specific-URI. This may wind up being |
| redone yet again if/when the underlying storage representation |
| changes.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>08/03/2001<br/><ref>Added: </ref>java/src/org/apache/xalan/lib PipeDocument.java<br/><ref>Committer's log entry: </ref>PipeDocument extension element (the pipeDocument method).<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/04/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java |
| java/src/org/apache/xpath NodeSet.java NodeSetDTM.java<br/><ref>Committer's log entry: </ref>Bug fixed regarding the current() function in the root template |
| (related to bug#1269). Bug was reported by David Marston |
| offline. The test for this is conf/copy/copy29. |
| |
| In TransformerImpl#applyTemplateToNode, create a NodeSetDTM and pass it to |
| m_xcontext.pushContextNodeList(cnl);. |
| In NodeSetDTM fix getCurrentNode so that it doesn't use m_next-1 |
| (which simply appears to be completely wrong). Do the same for |
| NodeSet... though I don't think this will be called anywhere in |
| Xalan.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/04/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm DTMAxisIterator.java |
| java/src/org/apache/xml/dtm/ref DTMAxisIteratorBase.java |
| DTMDefaultBaseIterators.java<br/><ref>Committer's log entry: </ref>Provide method for DTMAxisIterator to get the current root node |
| of the iteration.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/04/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/objects XObject.java<br/><ref>Committer's log entry: </ref>In response to regression posted on xalan-dev by John Gentilin |
| <johnglinux@eyecatching.com> |
| on 08/03/2001 06:49 PM. When the XNodeSet taks a DTMIterator, it |
| will call val.getDTMManager();, which will call LocPathIterator#getDTMManager, |
| which will call m_execContext..getDTMManager(), which means |
| that setRoot has to be called on the iterator before it is added to |
| XNodeSet. Thus, call setRoot on the OneStepIterator in |
| create(Object, XPathContext) before it is added to the XNodeSet. |
| The regression was related to fix for |
| http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2925.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/05/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes OneStepIterator.java<br/><ref>Committer's log entry: </ref>For the OneStepIterator(DTMAxisIterator iterator) constructor, |
| initialize the node tests to DTMFilter.SHOW_ALL (duh).<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/objects XObject.java<br/><ref>Added: </ref>java/src/org/apache/xpath/objects XObjectFactory.java<br/><ref>Committer's log entry: </ref>Move create methods from XObject to XObjectFactory, in response |
| to cyclic build problems encountered with javac 1.1.8.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils NamespaceSupport2.java<br/><ref>Committer's log entry: </ref>Moved anonomous class to PrefixEnumerator, in response |
| to problems encountered with 1.1.8 build. |
| Joe may want to fix this in another way, as |
| I'm sure the anon class is probably a bit |
| cheaper?<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath VariableStack.java<br/><ref>Committer's log entry: </ref>Address http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2972, |
| where it was throwing a NPE instead of reporting that the variable |
| was being accessed before it was bound (i.e. the variable was being |
| accessed inside an RTF for that same variable).<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer |
| TransformerHandlerImpl.java<br/><ref>Committer's log entry: </ref>Remove m_hasStarted variable and associated assertion.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref DTMDefaultBaseIterators.java<br/><ref>Committer's log entry: </ref>Addresses bug http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3001. |
| In the cloneIterator function of PrecedingIterator, the cloned array |
| was being sized for _maxAncestors, which defaults to 8. But if the |
| _stack was resized, it will copy more into the new stack than is |
| allocated. The solution is to allocate the new clone._stack array to |
| _stack.length.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>08/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils NamespaceSupport2.java<br/><ref>Committer's log entry: </ref>Don't create caches unless used (which I don't think they are, in Xalan).<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref DTMDefaultBaseIterators.java<br/><ref>Committer's log entry: </ref>Made _maxAncestors not static, as this is |
| not compatible with 1.1.8 (reported by |
| Gary Peskin).<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>08/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils NamespaceSupport2.java<br/><ref>Committer's log entry: </ref>Playing a hunch, I moved the Context objects out of NamespaceSupport2. |
| They're now a second class in the same file rather than being an inner class. |
| That reduces the size of the Context2 object, and its initialization time, by |
| removing the need for it to carry a reference to the NamespaceSupport2 |
| object that created it. |
| |
| Performance seems significantly improved... even (surprisingly!) on the |
| getDeclaredPrefixes operation. Memory usage also seems better, as |
| expected. |
| |
| NamespaceSupport2 is still acounting for about 5% |
| of the time spent in the ResultTreeHandler, according |
| to my latest trace. Apparently we are calling |
| getDeclaredPrefixes an obscenely large number of |
| times, and the Vector.elements call is adding up. We |
| may want to look at where this is being called from |
| and whether we can reduce the number of invocations.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>08/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer ResultTreeHandler.java<br/><ref>Committer's log entry: </ref>Performance improvement; avoid scanning the same list twice.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer |
| TransformerHandlerImpl.java TransformerImpl.java |
| java/src/org/apache/xalan/xslt Process.java |
| java/src/org/apache/xml/dtm/ref |
| IncrementalSAXSource_Filter.java |
| java/src/org/apache/xml/utils DefaultErrorHandler.java |
| java/src/org/apache/xpath/operations Variable.java<br/><ref>Committer's log entry: </ref>This checkin hopefully fixes many problems with bad diagnostics lately, but |
| at the expense of a slight change in behavior. The rule now is, the |
| DefaultErrorHandler never outputs location info for error and fatalError... |
| this has to be done |
| by the catcher of the exception. Convenience methods for this are |
| in DefaultErrorHandler#printLocation. This method will unwrap the |
| exception as close to the originating source as possible.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/07/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/extensions |
| XSLProcessorContext.java |
| java/src/org/apache/xml/dtm DTMIterator.java |
| java/src/org/apache/xml/dtm/ref DTMAxisIteratorBase.java |
| java/src/org/apache/xpath NodeSetDTM.java |
| java/src/org/apache/xpath/axes AttributeIterator.java |
| AxesWalker.java ChildIterator.java |
| ChildTestIterator.java DescendantIterator.java |
| FilterExprWalker.java LocPathIterator.java |
| OneStepIterator.java OneStepIteratorForward.java |
| ReverseAxesWalker.java UnionPathIterator.java |
| WalkingIteratorSorted.java |
| java/src/org/apache/xpath/objects XObjectFactory.java<br/><ref>Committer's log entry: </ref>Changes to allow some dynamic determination in WalkerIteratorSorted to |
| see if the nodes really need to be sorted. Added isDocOrdered() and |
| getAxis() to both DTMIterator and AxesWalker, and implemented |
| appropriate overloads in derived or implementing classes. In FilterExprWalker |
| return the contained DTMIterator's getAxis(). In WalkerIteratorSorted, |
| implement canBeWalkedInNaturalDocOrder() function that is called |
| from setRoot(...). If this function returns true, than don't sort the nodes |
| in setRoot, and in all other respects treat this as if it is a simple |
| WalkingIterator.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>08/07/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>Fix for bugzilla 1251. Make sure exceptions are thrown when we're on the main |
| thread.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/07/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes AxesWalker.java |
| WalkerFactory.java WalkingIteratorSorted.java<br/><ref>Committer's log entry: </ref>Eliminate do/while check for duplicates in AxesWalker#nextNode() |
| by using WalkingIteratorSorted for cases where both the preceding[-sibling] |
| and following[-sibling] axes are being walked, and for "@*/foo" patterns |
| ("@attr/foo" patterns still use WalkingIterator).<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>08/08/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates FuncFormatNumb.java<br/><ref>Committer's log entry: </ref>Fix bugzilla bug 3036 |
| (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3036). When no |
| xsl:decimal-format element is supplied in the composed stylesheet, the defaults |
| specified in the Recommendation section 12.3 should be used for the attribute |
| values, not locale-specific defaults.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>08/09/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref/sax2dtm SAX2DTM.java<br/><ref>Committer's log entry: </ref>Fix for bugzilla 3060 |
| (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3060). Prefixes and |
| namespaceURIs are kept in the same Vector, m_prefixMappings. The entries are |
| stored as pairs of vector elements. The even elements contain the prefix and |
| the odd elements contain the URI. In two routines, getPrefix and endElement, |
| the appropriate prefix or URI was being located in the Vector using an |
| indexOf. However, in this case where the prefix and the URI were the same, the |
| routine was looking for the URI but finding the prefix instead of the URI. It |
| tried tried to back up one to get the prefix and underflowed the Vector size.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>08/09/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer ResultTreeHandler.java |
| TransformerImpl.java<br/><ref>Committer's log entry: </ref>Implement ErrorHandler in ResultTreeHandler so that fatal errors can get |
| passed in to the SAXHandler. Also change the code in TransformerImpl to call |
| fatalError in case of an error instead of endDocument. (overlaps with URI |
| handling fix...)<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>08/09/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor |
| TransformerFactoryImpl.java |
| java/src/org/apache/xalan/transformer |
| TransformerIdentityImpl.java |
| java/src/org/apache/xml/utils SystemIDResolver.java<br/><ref>Committer's log entry: </ref>Fix code to handle absolute paths from unix systems. This fix is part of an |
| ongoing process and is just meant to fix a few pending bugs. More changes are |
| expected in this area.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>08/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor XSLProcessorVersion.java<br/><ref>Committer's log entry: </ref>Change version for xalan2.2.D9 build<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>08/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemElement.java |
| java/src/org/apache/xalan/transformer ResultTreeHandler.java |
| java/src/org/apache/xml/utils DefaultErrorHandler.java<br/><ref>Committer's log entry: </ref>ResultTreeHandler was pushing a new namespace context but failing to note |
| that result in more pushes than pops. Cleaned up the execute() method of |
| ElemElement to make it more understandable (to me) and added a few comments. |
| The DefaultErrorHandler was not flushing Writers that it created. Since the |
| Writers are never closed (and cannot be as there is no close method), error |
| messages were failing to appear.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>08/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm DTMManager.java<br/><ref>Committer's log entry: </ref>Increasing the number of bits used to identify DTM nodes, at the expense of |
| decreasing the number of DTMs that a DTMManager can track simultaneously. Some |
| other code has been updated to track this change (and to better track posible |
| future changes), as have the IDKEY testcases.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>08/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref DTMDefaultBase.java |
| DTMDocumentImpl.java DTMManagerDefault.java<br/><ref>Committer's log entry: </ref>Increasing the number of bits used to identify DTM nodes, at the expense of |
| decreasing the number of DTMs that a DTMManager can track simultaneously. Some |
| other code has been updated to track this change (and to better track posible |
| future changes), as have the IDKEY testcases.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>08/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/functions FuncGenerateId.java<br/><ref>Committer's log entry: </ref>Increasing the number of bits used to identify DTM nodes, at the expense of |
| decreasing the number of DTMs that a DTMManager can track simultaneously. Some |
| other code has been updated to track this change (and to better track posible |
| future changes), as have the IDKEY testcases.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>08/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath NodeSetDTM.java<br/><ref>Committer's log entry: </ref>Try to support getRoot. Fixes problem with TransformStateTest.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>08/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes WalkerFactory.java<br/><ref>Committer's log entry: </ref>Fix problem with duplicate nodes produced from a walking iterator<br/><br/></li></ul><note>This release includes no updates of the compatibility source code (now deprecated).</note> |
| </s3> |
| <s3 title="Changes for &xslt4j; 2.2.D8"> |
| <p> Core (Non-XSLTC) source code updates:</p><ul><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/20/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql SQLDocument.java<br/><ref>Committer's log entry: </ref>Code Update |
| Submitted by:John Gentilin<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/20/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql SQLDocument.java<br/><ref>Committer's log entry: </ref>Fixed DTM.NULL compile error<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>07/20/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TreeWalker2Result.java<br/><ref>Committer's log entry: </ref>Redundant test removed, possibly redundant code flagged for %REVIEW%<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>07/20/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql SQLDocument.java |
| java/src/org/apache/xalan/transformer |
| TransformerHandlerImpl.java |
| java/src/org/apache/xml/dtm/ref DTMDefaultBase.java |
| DTMDocumentImpl.java DTMManagerDefault.java |
| IncrementalSAXSource.java |
| IncrementalSAXSource_Filter.java |
| IncrementalSAXSource_Xerces.java |
| java/src/org/apache/xml/dtm/ref/dom2dtm DOM2DTM.java |
| java/src/org/apache/xml/dtm/ref/sax2dtm SAX2DTM.java |
| java/src/org/apache/xml/utils SuballocatedIntVector.java<br/><ref>Committer's log entry: </ref>IncrementalSAXSource replaces CoroutineSAXParser -- simpler API, |
| hence less risk of programming errors introducing timing windows. I hope. |
| A few performance-related tweaks are also included in this check-in. |
| Only very minor gains are expected.<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/22/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql ObjectArray.java |
| SQLDocument.java<br/><ref>Committer's log entry: </ref>Project Update<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>07/23/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>Oops.Should have been checked in as part of the IncrementalSAXSource cutover. |
| Sorry!<br/><br/></li><li><ref>Committed by </ref>costin@apache.org<ref> on </ref>07/23/2001<br/><ref>Modified: </ref>java build.xml |
| java/src/org/apache/xml/dtm/ref |
| IncrementalSAXSource_Filter.java |
| java/src/org/apache/xml/utils/synthetic JavaUtils.java<br/><ref>Committer's log entry: </ref>3 small fixes to the build process ( to make it work with jdk1.4 and crimson) |
| |
| - exclude IncrementalSAXSource_Xerces if xerces is not detected |
| - comment-out the "main" in IncrementalSAXSource_Filter.java ( it is a |
| test, but has deps on xerces ) |
| - don't try to load the compiler in syntetic/JavaUtils. This is a mess, |
| it was debated on tomcat-dev and ant-dev, as you may know some people |
| decided to remove the internal compiler class ( sun.tools.javac.Main ), |
| and that brakes jasper, ant and now xalan. |
| |
| It seems right now the only portable way to run the compiler is via command |
| line call in a separate process ( jikes can easily make up for the |
| overhead of creating a new process and doesn't leave garbage ). |
| |
| Question: is synthetic used ? Seems like a very usefull package, but if |
| xalan is not using it it might be better to move it to xml-commons or |
| jakarta-commons or some other place.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/24/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql SQLDocument.java<br/><ref>Committer's log entry: </ref>Don't set m_level anymore, as it looks like Joe commented out it's |
| initialization. m_level is no longer called by Xalan, and the implementation |
| can calculate it when it is called.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>07/24/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer |
| TransformerIdentityImpl.java<br/><ref>Committer's log entry: </ref>Fixed bug 2758 (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2758). The |
| flag indicating that a call to startDocument() in the resultContentHandler was |
| necessary was not being reset for multiple transforms.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>07/25/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref/sax2dtm SAX2DTM.java<br/><ref>Committer's log entry: </ref>Fix bug 2727 (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2727). |
| Attributes which contain a namespace prefix are indicated by placing a negative |
| number in the appropriate entry in the m_dataOrQName array. The absolute value |
| of this number is an entry in m_data. However, in this example, there were no |
| text nodes before the first namespaced attribute so the entry in m_data had an |
| array index of 0. This resulted in an entry of zero, not a negative number, in |
| m_dataOrQName. This situation got several routines which tested for < 0 |
| confused. I looked at several ways of fixing this but decided to just always |
| allocate m_data.elementAt(0) entry to a dummy entry. The other solutions |
| involved runtime checking which could slow down this piece of code and I felt |
| that wasting one entry was worth it to not slow down the run time.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>07/26/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/serialize |
| WriterToUTF8Buffered.java<br/><ref>Committer's log entry: </ref>Fix bugzilla bug 2639 |
| (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2639) where buffer was |
| overflowing because the expansion of the Unicode characters into multiple UTF8 |
| characters was not being properly taken into account. Many thanks to |
| Gunnlaugur Thor Briem for his "multiply by three" trick.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/26/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer NodeSorter.java<br/><ref>Committer's log entry: </ref>Commented out NumberFormat m_formatter = NumberFormat.getNumberInstance();. |
| |
| Mukund reported: |
| |
| a minor improvement for alphabetize.xsl is to comment out the line |
| |
| //NumberFormat m_formatter = NumberFormat.getNumberInstance(); |
| |
| in NodeSorter.java. The variable m_formatter does not seem to be used |
| anywhere, and the performance difference is: |
| |
| Before: alphabetize 10 90 5108 196 156 34.58 |
| OK |
| After : alphabetize 10 70 4316 196 156 |
| 40.93 OK<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/res XSLTInfo.properties<br/><ref>Committer's log entry: </ref>2.2.D8<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor XSLProcessorVersion.java<br/><ref>Committer's log entry: </ref>2.2.D8<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer NodeSortKey.java<br/><ref>Committer's log entry: </ref>Submitted fix for http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2851.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/xslt Process.java<br/><ref>Committer's log entry: </ref>Just added some stuff to diagnose bugs for flavor th.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes WalkerFactory.java |
| java/src/org/apache/xpath/compiler Compiler.java |
| java/src/org/apache/xpath/patterns |
| ContextMatchStepPattern.java StepPattern.java<br/><ref>Committer's log entry: </ref>These are changes submitted (offline) by Mukund Raghavachari/Watson/IBM@IBMUS. |
| |
| This fixes a bug with match="chapter//footnote[1]" patterns. |
| |
| The main change here is minor to remove the automatic attachment of parent::* |
| to simple step patterns. |
| |
| He has re-implemented executePredicates to be |
| more efficient. Given a pattern such as row[6], it |
| does not iterate over the entire axis until it reaches |
| the node to see if it is the sixth node. Rather, |
| starting from the current node, it works backwards |
| (preceding siblings) until it either runs out of nodes |
| or finds more than six nodes that match the |
| predicate [I can explain it better if desired]. |
| This optimization improves performance slightly |
| overall. It helps decoy and patterns most (by |
| about 10%). |
| |
| The other optimization that I implemented was the |
| following. For a pattern foo[][3][][4] ..., where more |
| than one predicate is a number (position check), |
| in checking the predicate [4], the fact that the |
| current node has passed foo[][3] implies that it is |
| the only node that is the third node among its |
| siblings that passes foo[]. Therefore, any |
| subsequent position checks can be true if and |
| only if the position is [1]. This optimization is not |
| used by the xsltmark benchmarks and so does |
| not offer any performance benefits.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes DescendantIterator.java<br/><ref>Committer's log entry: </ref>Fix for http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1336<br/><br/></li></ul><note>This release includes no updates of the compatibility source code (now deprecated).</note> |
| </s3> |
| <s3 title="Changes for &xslt4j; 2.2.D7"> |
| <p> Core (Non-XSLTC) source code updates:</p><ul><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/03/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref DTMManagerDefault.java<br/><ref>Committer's log entry: </ref>Since the real root of our tree may be a DocumentFragment, we need to |
| use getParent to find the root, instead of getOwnerDocument. Otherwise |
| DOM2DTM#getHandleOfNode will be very unhappy. |
| Result of report via private mail by Carsten Ziegeler of breakage |
| in Cocoon.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/05/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/serialize SerializerToHTML.java |
| SerializerToXML.java<br/><ref>Committer's log entry: </ref>Made m_maxCharacter, accumDefaultEscape, |
| accumDefaultEntity, and m_isRawStack |
| protected by request from Johannes Farrenkopf |
| and Frank Nestel.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/05/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/functions FuncNormalizeSpace.java<br/><ref>Committer's log entry: </ref>In executeCharsToContentHandler check first for |
| DTM.NULL before trying to get the DTM.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/05/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils FastStringBuffer.java<br/><ref>Committer's log entry: </ref>Fix bug reported by "Carsten Ziegeler" <cziegeler@sundn.de>. |
| Test for this is whitespace23.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>07/05/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils SuballocatedIntVector.java<br/><ref>Committer's log entry: </ref>Drop some bounds tests for cases which shouldn't arise in the first place, |
| since this is an inner-loop method.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>07/05/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils SuballocatedByteVector.java |
| SuballocatedIntVector.java<br/><ref>Committer's log entry: </ref>Synch SuballocatedByteVector with changed SuballocatedIntVector<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/05/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref CoroutineSAXParser.java<br/><ref>Committer's log entry: </ref>Revert back to throwing a shutdownException if (arg == null) in co_yield. I |
| see this |
| occur if the parser is Crimson with output\output01, and it causes |
| a hang if the shutdownException is not thrown.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/serialize SerializerToXML.java<br/><ref>Committer's log entry: </ref>Make accumDefaultEntity and accumDefaultEscape non-final.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes ChildTestIterator.java |
| OneStepIterator.java |
| java/src/org/apache/xpath/functions FuncExtFunction.java<br/><ref>Committer's log entry: </ref>Fix for John G. for the SQL extension: handle return types of |
| DTM and DTMAxisIterator.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/09/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>In executeChildTemplates, somehow there was a popMode without |
| a corresponding pushMode. The pushMode was added. |
| Addresses bug posted by Stephane Bailliez <sbailliez@imediation.com> |
| on the xalan-dev list on 07/09/2001 07:28 AM.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>07/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/extensions ExpressionContext.java |
| java/src/org/apache/xalan/templates StylesheetRoot.java |
| java/src/org/apache/xpath VariableStack.java |
| XPathContext.java<br/><ref>Committer's log entry: </ref>Resolve bugzilla 2355 |
| <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2355>. To make the |
| functionality clearer, I've changed the method name from getVariable to |
| getVariableOrParam since the routine will pick up either one. Also fixed a |
| bug where top level variables and parameters were not getting marked as such.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>07/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib Extensions.java |
| java/src/org/apache/xpath XPathContext.java<br/><ref>Committer's log entry: </ref>Resolve bugzilla 2523 |
| <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2523>. evaluate extension |
| function was not refactored with DTM. Also need to add function to |
| XPathContext.XPathExpressionContext to allow an extension to obtain the |
| associated XPathContext.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>07/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes DescendantIterator.java<br/><ref>Committer's log entry: </ref>Fix problem with descendant-or-self and from root pattern. When from root, |
| descedant or self was not recognized.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>07/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref/dom2dtm DOM2DTM.java<br/><ref>Committer's log entry: </ref>Quick patch to handle case where someone wants to build a DTM from |
| an Element rather than from a Document. The Attr handling might want to |
| move down into addNode. |
| |
| This opens several cans of worms -- what if the next user wants the |
| root of their DTM to be an EntityReference node, which has no DTM |
| node equivalent -- but we'll eat those when we get to them.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>07/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib Extensions.java<br/><ref>Committer's log entry: </ref>Modify distinct() extension so that it no longer relies on DOMHelper which is |
| deprecated but uses ExpressionContext.toString().<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/res XSLTErrorResources.java |
| java/src/org/apache/xalan/trace PrintTraceListener.java |
| java/src/org/apache/xalan/transformer TransformerImpl.java |
| java/src/org/apache/xalan/xslt Process.java |
| java/src/org/apache/xml/dtm DTM.java |
| java/src/org/apache/xml/dtm/ref DTMDocumentImpl.java |
| ExpandedNameTable.java |
| java/src/org/apache/xml/dtm/ref/dom2dtm DOM2DTM.java |
| java/src/org/apache/xml/dtm/ref/sax2dtm SAX2DTM.java<br/><ref>Added: </ref>java/src/org/apache/xalan/lib NodeInfo.java |
| java/src/org/apache/xalan/transformer XalanProperties.java |
| java/src/org/apache/xml/dtm/ref NodeLocator.java<br/><ref>Committer's log entry: </ref>Application of patch submitted by Ovidiu Predescu <ovidiu@cup.hp.com> |
| for file, line, column number information for XML source document. |
| |
| [A made one change: m_sourceSystemId, m_sourceLine, and |
| m_sourceColumn are not created with the member variable |
| initializer, since they are initialized in setProperty.] |
| |
| The following patch is a rework of a previous patch I've submitted on |
| May 24 against the Stree model, current at that time. This time the |
| patch is against the DTM model, and makes use of DTM features to |
| optimize the lookup time and storage requirements. I hope this time |
| the patch gets incorporated in the CVS repository, before any major |
| rework happens again ;-). |
| |
| As with the previous patch, there is no overhead in space or time if |
| source information is not needed. |
| |
| From a user perspective, this feature can be turned on by passing the |
| -L flag to Xalan when invoking it from the command |
| line. Programmatically you can also enable it by invoking the |
| setProperty method on the TransformerImpl: |
| |
| TransformerImpl impl = ((TransformerImpl) transformer); |
| |
| impl.setProperty(org.apache.xalan.transformer.XalanProperties.SOURCE_LOCATION, |
| Boolean.TRUE); |
| |
| A Transformer "property" is different from a "feature": while a |
| feature is specific to all the transformer instances and usually |
| refers to an implementation aspect, a property is a runtime capability |
| that is set per Transformer instance. Currently the only property |
| added by this patch is the source location in the XML source document. |
| |
| The patch adds two methods to the DTM interface: |
| |
| public void setProperty(String property, Object value); |
| public SourceLocator getSourceLocatorFor(int node); |
| |
| The second method is used to obtain the source location given a node |
| handle. |
| |
| There are two ways you can make use of the source location. The first |
| one is from within a stylesheet, where you can have something like |
| this: |
| |
| <xsl:stylesheet |
| xmlns:xsl="http://www.w3.org/1999/XSL/Transform" |
| xmlns:nodeinfo="xalan://org.apache.xalan.lib.NodeInfo" |
| version="1.0"> |
| |
| <xsl:template match="*"> |
| //node <xsl:value-of select="name()"/> |
| //file <xsl:value-of select="nodeinfo:systemId()"/> |
| //line <xsl:value-of select="nodeinfo:lineNumber()"/> |
| //column <xsl:value-of select="nodeinfo:columnNumber()"/> |
| <xsl:apply-templates/> |
| </xsl:template> |
| |
| </xsl:stylesheet> |
| |
| If no arguments are passed to the systemId(), lineNumber() or |
| columnNumber() functions, the corresponding information of the current |
| context node is returned. A node can be passed as argument to the |
| above functions, in which case the corresponding information about |
| that node is returned. If a node set containing multiple nodes is |
| passed as argument, only the information of the first node in the set |
| is returned. |
| |
| The second way of obtaining the source location is |
| programmatically. Given a Node instance, one can obtain the owner DTM |
| and the node handle (an integer) that represents the |
| node. Unfortunately I didn't see any way of hiding this: if you find |
| one please let me know and I'll fix it. |
| |
| The following example is extracted from PrintTraceListener and |
| illustrates the API: |
| |
| Node sourceNode = ev.m_sourceNode; |
| int nodeHandler = ((DTMNodeProxy)sourceNode).getDTMNodeNumber(); |
| SourceLocator locator = ((DTMNodeProxy)sourceNode).getDTM() |
| .getSourceLocatorFor(nodeHandler); |
| |
| m_pw.println("Selected source node '" + sourceNode.getNodeName() |
| + "', at " + locator);<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>07/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/compiler Compiler.java<br/><ref>Committer's log entry: </ref>Fix bug 2175 <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2175> by |
| adding the current time to the method key to ensure method key uniqueness. |
| Multiple Compilers were getting the same hashCode, particularly in Visual Age |
| for Java, due to aggressive garbage collection. Added the current time in |
| mills to distinguish between the different functions being compiled.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>07/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemVariable.java |
| StylesheetRoot.java |
| java/src/org/apache/xpath VariableStack.java |
| java/src/org/apache/xpath/operations Variable.java<br/><ref>Committer's log entry: </ref>Resolve bugzilla 2355 |
| <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2355>. Added code to |
| populate m_index for global variables and parameters. If the backward search |
| for templates reaches the top level, use the list of composed top-level |
| variables and parameters from StylesheetRoot.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref DTMNodeProxy.java<br/><ref>Committer's log entry: </ref>Now implements DocumentFragment.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>07/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/res XSLTInfo.properties<br/><ref>Committer's log entry: </ref>Updated version to 2.2.0.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>07/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor XSLProcessorVersion.java<br/><ref>Committer's log entry: </ref>Updated version to 2.2.0.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref DTMNodeProxy.java<br/><ref>Committer's log entry: </ref>Fixed very ugly bug, left-over from DTM1, in getValue, where +1 was being |
| added per the old attribute structure of DTM1.<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/12/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql ConnectionPool.java |
| DefaultConnectionPool.java PooledConnection.java |
| QueryParameter.java XConnection.java<br/><ref>Added: </ref>java/src/org/apache/xalan/lib/sql ConnectionPoolManager.java |
| ObjectArray.java SQLDocument.java |
| SQLErrorDocument.java<br/><ref>Removed: </ref>java/src/org/apache/xalan/lib/sql Column.java |
| ColumnAttribute.java ColumnData.java |
| ColumnHeader.java ExtensionError.java Row.java |
| RowSet.java SQLExtensionError.java |
| StreamableNode.java XConnectionPoolManager.java |
| XStatement.java<br/><ref>Committer's log entry: </ref>First round of changes to port DOM mode to DTM Mode |
| Submitted by: John Gentilin mailto://johng@apache.org<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>07/12/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref/sax2dtm SAX2DTM.java<br/><ref>Committer's log entry: </ref>Check if locator property is set before trying to use locator fields<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>07/12/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/trace PrintTraceListener.java<br/><ref>Committer's log entry: </ref>Don't print locator message if locator is null<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/12/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer |
| TransformerHandlerImpl.java<br/><ref>Committer's log entry: </ref>In startDocument, run m_contentHandler.startDocument before you start the |
| thread.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/12/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>Call wait for initial events before the the transform is started.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/12/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref CoroutineSAXParser.java<br/><ref>Committer's log entry: </ref>Allow co_yield to be called after the parse has finished.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/12/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql SQLDocument.java |
| SQLErrorDocument.java<br/><ref>Committer's log entry: </ref>Added setProperty and getSourceLocatorFor empty methods.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>07/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref/dom2dtm DOM2DTM.java<br/><ref>Committer's log entry: </ref>Fix problem reported by Carsten Ziegeler <cziegeler@sundn.de>. Using |
| ApplyXPath (or doing a transformation) with DOM input was resulting in an NPE |
| due to declareNamespaceInContext() being called before setting m_exptype which |
| is needed by declareNamespaceInContext().<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer |
| TransformerHandlerImpl.java<br/><ref>Committer's log entry: </ref>Add pauseForTransformThreadStartup. Call this in startDocument just |
| after starting the transform thread. This should get rid of any variability |
| with racing threads.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/extensions |
| XSLProcessorContext.java<br/><ref>Committer's log entry: </ref>Fix problem reported by jason heddings <Jason.Heddings@Sun.COM>. |
| |
| "In v2.0.1, I was able to pass a Node to this function and have the node |
| be copied to the result tree (as expected). In the source code for |
| XSLProcessorContext, it appears that the only objects that can be sent |
| to the result tree are XObjects. Everything else is converted to a |
| String. So for instance, I can no longer create a ProcessingInstruction |
| and pass it to the result tree via this method since the PI is simply |
| converted to a String."<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/serialize SerializerToHTML.java<br/><ref>Committer's log entry: </ref>Application of patch submitted by Benjamin Riefenstahl |
| <Benjamin.Riefenstahl@ision.net> |
| |
| Motivation: We are using Xalan to generate HTML pages. We have the |
| requirement to integrate code for ad banners. The ad server provider |
| has written the code to use with compatibility to NetScape 4 in mind. |
| The code uses the NetScape proprietory <LAYER> element and <IFRAME> |
| elements for other browsers. The SRC attributes of these elements |
| contain URLs with several URL parameters separated by '&', as is the |
| common convention. |
| |
| Problem: The code is integrated in our XSL stylesheets. In the |
| stylesheet the '&' has to be written as the entity '&amp;'. That's |
| ok. The problem is that in the output the '&' is also written as |
| '&amp;' which is not ok, because NetScape doesn't understand that. |
| OTOH the same URL is written with '&' when used in an <A> element. |
| |
| Solution: This goes down to a different handling of attribute values |
| in the class SerializeToHTML, depending on whether the attribute in |
| question is known to contain a URI or not. Xalan knows this for <A> |
| but not for <LAYER> and <IFRAME>. When I compare the list in |
| SerializeToHTML.java with the HTML specs, I find a couple of other |
| missing URI attributes in SerializeToHTML.java. When I add the |
| missing pieces, the generation works fine. |
| |
| Patch: Here is the patch (diff -c) for xalan-j_2_2_D6. I also have |
| one for xalan-j_2_0_1 which is the version I actually tested this |
| with. Please let me know if this is insufficient or the patch is |
| wrong or if there is something else I can do to fix this problem.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref/dom2dtm DOM2DTM.java<br/><ref>Committer's log entry: </ref>On code review of previous checkin from Gary P., we determined there |
| was a problem with the point at which type was declared a |
| DTM.NAMESPACE_NODE. So that part was moved back up (actuall |
| a bit higher than where it was before), |
| and the call to declareNamespaceInContext was moved a bit |
| further down.<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/15/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql XConnection.java<br/><ref>Committer's log entry: </ref>Project Update |
| Submitted by: John Gentilin mailto://johng@apache.org<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/15/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql SQLDocument.java<br/><ref>Committer's log entry: </ref>Project Update |
| Submitted by: John gentilin mailto://johng@apache.org<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/15/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql SQLDocument.java<br/><ref>Committer's log entry: </ref>Fixup from previous check-in, defined new |
| functions. |
| Submitted by: John Gentilin mailto://johng@apache.org<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/15/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql SQLDocument.java<br/><ref>Committer's log entry: </ref>Project Update<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/15/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql SQLDocument.java<br/><ref>Committer's log entry: </ref>reduced Attribute's for testing<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>07/16/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref/sax2dtm SAX2DTM.java<br/><ref>Committer's log entry: </ref>Minor hack to catch an attribute value being null.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>07/17/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemNumber.java |
| java/src/org/apache/xalan/transformer Counter.java |
| CountersTable.java KeyRefIterator.java |
| java/src/org/apache/xml/dtm/ref/dom2dtm DOM2DTM.java |
| java/src/org/apache/xpath NodeSetDTM.java |
| java/src/org/apache/xpath/axes LocPathIterator.java |
| UnionPathIterator.java WalkingIteratorSorted.java |
| java/src/org/apache/xpath/objects XNodeSet.java |
| XRTreeFrag.java<br/><ref>Committer's log entry: </ref>Add new parameter to NodeSetDTM constructor. We need to have a DTMManager on |
| hand. Change code to use the new constructors.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>07/17/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref/dom2dtm DOM2DTM.java<br/><ref>Committer's log entry: </ref>OOps! Back out this last change. Old code on my machine!!!<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>07/17/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql SQLDocument.java<br/><ref>Committer's log entry: </ref>Fixed a few bugs, almost there |
| Submitted by: John Gentilin mailto://johng@apache.org<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>07/18/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref CoroutineManager.java |
| CoroutineSAXParser.java |
| CoroutineSAXParser_Xerces.java<br/><ref>Added: </ref>java/src/org/apache/xml/dtm/ref IncrementalSAXSource.java |
| IncrementalSAXSource_Filter.java |
| IncrementalSAXSource_Xerces.java<br/><ref>Committer's log entry: </ref>Starting to phase out Coroutine*Parser* in favor of IncrementalSAXSource*. |
| The latter simplifies the code, and should help us avoid some of the |
| confusion that can arise in using the older tools. |
| |
| Most importantly, it greatly simplifies the calling sequences, by discarding |
| the "which file do you want to parse" and "do you want to parse any more |
| files" transactions. These now operate _only_ as filters, and only as single |
| -use (though in fact the Xerces-specific version is reusable, and we may |
| reintroduce that feature in the generic filtering version at a later date). |
| |
| Note too that we have swept the CoroutineManager completely |
| under the covers of the filter's API. There's no particular reason to expose |
| that implementation detal to the outside world. |
| |
| Still to be done: Rework the rest of Xalan to use the new code.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>07/18/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref CoroutineParser.java<br/><ref>Committer's log entry: </ref>Starting to phase out Coroutine*Parser* in favor of IncrementalSAXSource*. |
| See comment in previous check-in; I just missed this one....<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>07/18/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/dtm/ref DTMStringPool.java<br/><ref>Committer's log entry: </ref>doc.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>07/18/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/res XSLTInfo.properties<br/><ref>Committer's log entry: </ref>2.2.D7<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>07/18/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor XSLProcessorVersion.java<br/><ref>Committer's log entry: </ref>2.2.D7<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>07/18/2001<br/><ref>Removed: </ref>java/src/org/apache/xml/dtm/ref DTMBuilder.java<br/><ref>Committer's log entry: </ref>Obsolete<br/><br/></li></ul><note>This release includes no updates of the compatibility source code (now deprecated).</note> |
| </s3> |
| <s3 title="Changes for &xslt4j; 2.2.D6"> |
| <p><em>Important: Xerces has added a number of DOM level-3 methods to its DOM interfaces. The DOM level-3 proposal |
| is currently a working draft (it is not yet a W3C recommendation), and Xalan does not support these new methods. |
| To run Xalan in the JDK 1.1.8 platform, you must put xalan.jar (with its DOM level-2 interfaces) in front of |
| xerces.jar on the system class path. If you want to rebuild Xalan (on JDK 1.1.8 or higher), you must put Xalan |
| in front of xerces.jar on the system class path.</em></p> |
| |
| <p>This beta release includes the following non-XSLTC code changes:</p> |
| <ul> |
| <li>Costin Manolache has slightly modified the CoRoutine stuff so that a you can compile and run everything but the CoRoutineXercesParser without having Xerces on the classpath.<br/><br/></li> |
| <li>Joseph Kesselman added chunked int array stuff to address our scaling problems that Mukund & co. uncovered. This was a fairly mechanical, but still substantial, change. No bugs have yet been discovered that relate to this. This is probably the most controversial change.<br/><br/></li> |
| <li>The Process class now outputs incrementally if the output is standard out. This is mostly for testing purposes, but it makes general sense.<br/><br/></li> |
| <li>Bug was fixed with setting the incremental flag in TransformerFactoryImpl. Clearly the change was made but never tested. Simply a missing 'else'.<br/><br/></li> |
| <li>Fix for Bugzilla Bug 2275, Xalan did not fire the right templates. This was substantial and somewhat risky. Xalan had several problems related to the last() function. Fixes cover four axes files.<br/><br/></li> |
| <li>Change PrintTraceListener to output the file, as well as the line numbers. This is really a feature change, but simple, and aids diagnosing problems with multi-part stylesheets.<br/><br/></li> |
| <li>XPath fix: the XPath API wasn't working correctly due to a problem with with NodeSet/NodeIterator adapters. This fix ended up interacting quite a bit with the #2275 fix.<br/><br/></li> |
| <li>Fix for the Norm Walsh bug posted 06/20/2001: iterators weren't always being cloned correctly from the variable value stack. This fix is not without some risk, though we haven't seen any problems since Scott Boag made it.<br/><br/></li> |
| <li>David Bertoni added missing html element properties to SerializerToHTML.java.<br/><br/></li> |
| <li>Shance Curcuru modified TransformerFactoryImpl.setAttribute() to accept a String ("true" or "false") as well as a Boolean object to set the value of a Boolean attribute.<br/><br/></li> |
| <li>TransformerHandlerImpl was threading when incrementality is turned off. Scott Boag has fixed this bug.</li> |
| </ul> |
| </s3> |
| <anchor name="dtm"/> |
| <s3 title="Changes for &xslt4j; 2.2.D2"> |
| <p>This release includes the following changes:</p> |
| <ul> |
| <li>Deprecation of the <link idref="usagepatterns" anchor="compat">Xalan-Java 1 compatiblity API</link></li> |
| <li>The DTM</li> |
| <li>Other optimization work</li> |
| </ul> |
| <p>The primary focus of the 2.2 Developer releases is incorporation of all our work over the past several months on the Document Table |
| Model (<link idref="dtm">DTM</link>).</p> |
| |
| <p>As a result of the changes in *internal* api, you may encounter problems with extensions. We have done some bug fixing in support |
| for extensions since 2.2.D1. John Gentilin is working on fixing the SQL library extension,which currently is broken. Please report |
| any problems you find (see <link anchor="bugs">bugs</link>).</p> |
| |
| <p>The DTM and related work provides faster performance and less accumulation of garbage... though it is an |
| ongoing battle. Brief summary:</p> |
| <ul> |
| <li>The DTM identifies nodes with 32-bit integer handles. |
| The DTM has many features, including direct character dispatch to SAX2, |
| native DTM iterators and "traversers", multiple document management, etc.<br/><br/></li> |
| <li>Joe Kesselman's CoRoutine parsers, which are in a threaded SAX flavor |
| and in a Xerces parseMore() flavor (no threads). These do away with the |
| "race" conditions that occured in the original code, and should make Xalan |
| much more robust.<br/><br/></li> |
| <li>*Much* more robust XPath itteration. The "waiting" iterators of old are |
| no more, and good riddance. There is stil lots more we want to do with |
| this mechanism. (There is something here called MatchIterators, but it's |
| not being used yet for various reasons. We will be taking advantage of |
| these down the line.)<br/><br/></li> |
| <li>A fair amount of XObject creation reduction. You can now get boolean, |
| number, nodeset, and string values directly from an Expression, instead of |
| going through an XObject.<br/><br/></li> |
| <li>XMLString, which allows us to work with string objects that don't wrap |
| Java's String object. These objects get their character data from an array or |
| Fast String Buffer.<br/><br/></li> |
| <li>Serializers now only do internal buffering if they know they are writing |
| to a FileStream.<br/><br/></li> |
| <li>The variable stack mechanism has been redisigned, so that it is no |
| longer so interpretive, and we believe it is much more robust.<br/><br/></li> |
| <li> Some small amount of stylesheet rewriting (but not yet redundent |
| expression elimination), in particular to reduce full RTF creation and |
| interpretation.</li> |
| </ul> |
| <p>&xslt4j; implements two DTM performance features that you can control with the TransformerFactory |
| <jump href="apidocs/javax/xml/transform/TransformerFactory.html#setAttribute(java.lang.String, java.lang.Object)">setAttribute()</jump> |
| method. See <link idref="dtm" anchor="settings">DTM performance settings</link></p> |
| </s3> |
| <s3 title="Changes for &xslt4j; 2.1.0"> |
| <p>This release includes a number of bug fixes to &xslt4j; and TrAX. |
| We have also enhanced the ApplyXSLT servlet. It can now be set up to use a compiled Templates object to respond to multiple |
| client transformation requests involving the same stylesheet.</p> |
| <!--This XML fragment contains a list of source code updates to place in an <s3> section of readme.xml--><p>Core source code updates:</p><ul><li><ref>Committed by </ref>costin@apache.org<ref> on </ref>03/16/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor StylesheetHandler.java |
| java/src/org/apache/xpath Expression.java XPath.java |
| XPathContext.java |
| java/src/org/apache/xpath/compiler Compiler.java |
| XPathParser.java<br/><ref>Committer's log entry: </ref>Renamed "assert()" to "assertion()". |
| |
| Assert can be a keyword, and brake the compilation.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>03/19/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer KeyWalker.java<br/><ref>Committer's log entry: </ref>Throw an error message if the key name in a key function was not defined<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>03/20/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils FastStringBuffer.java<br/><ref>Committer's log entry: </ref>Reworked "chunk growth" algorithm again. Growing mode not |
| yet adequately tested, but fixed-size mode (which is what Xalan |
| is currently using) is simpler code and shows improved performance.<br/><br/></li><li><ref>Committed by </ref>curcuru@apache.org<ref> on </ref>03/20/2001<br/><ref>Added: </ref>java/src/org/apache/xalan/xslt EnvironmentCheck.java<br/><ref>Committer's log entry: </ref>Utility class to check your JVM environment for common problems<br/><br/></li><li><ref>Committed by </ref>curcuru@apache.org<ref> on </ref>03/22/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/xslt EnvironmentCheck.java<br/><ref>Committer's log entry: </ref>Added more .jar sizes to jarVersions listing<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>03/22/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils FastStringBuffer.java<br/><ref>Committer's log entry: </ref>We've reworked the algorithm again. The fixed-chunk-size mode (initial |
| and max. chunk sizes equal) runs essentially unchanged, though with a |
| few cycles less overhead. The variable-chunk-size mode now uses a |
| recursive-encapsulation scheme, where the first chunk may itself be a |
| FastStringBuffer whose total length equals one chunk; every so often |
| we push the existing data down one level and restart with a larger |
| chunk size. The new scheme has been stress-tested and is apparently |
| working. At this writing, however, Xalan uses only the fixed-size |
| mode (initial size equals max size), and no effort has been made to |
| find the optimial values for the tuning parameters. It does appear |
| likely that the best values will vary with usage patterns, but we hope |
| to find a good compromise. |
| |
| I'll probably be putting this aside for a while to work on other things. |
| If someone wants to experiment with varying the block sizes and |
| how frequently they grow, and suggest good performance/memory |
| tradeoff points, go for it!<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>03/22/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils FastStringBuffer.java<br/><ref>Committer's log entry: </ref>Minor tweak to the javadoc.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>03/23/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils FastStringBuffer.java<br/><ref>Committer's log entry: </ref>reset() versus setLength(0).<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/26/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemForEach.java<br/><ref>Committer's log entry: </ref>Fix for bug# 1116, getMatchedTemplate throws ClassCastException. |
| Don't push template unless it is a xsl:template.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/26/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates OutputProperties.java<br/><ref>Committer's log entry: </ref>Patches submitted by Patrick Moore <patrickm@rioport.com> |
| on 03/15/2001 01:25 PM: |
| |
| This proposed change does a number of things: |
| |
| 1. Problem: HTML output method does not uses XML output properties as |
| default. |
| |
| In both org/apache/xalan/templates/output_html.properties and in the java |
| doc for |
| org/apache/xalan/templates/OutputProperties#getDefaultMethodProperties(Strin |
| g) It specifically states that all OutputProperties use the |
| output_xml.properties as a base. In the code this is not true for html. This |
| is now changed to match the comments |
| |
| 2. Problem: unclear IOException. |
| |
| If there was a problem loading the XML properties file. The wrapped |
| exception now will say which file was trying to be loaded. If the file did |
| not exist I was getting a very strange "Stream closed" IOException message. |
| |
| 3. Problem: the streams were not closed after reading the property file. |
| |
| Fixed. |
| |
| 4. Problem: the double-check locking mechanism does not work in Java (see |
| bug #919) |
| |
| <http://www.javaworld.com/javaworld/jw-02-2001/jw-0209-toolbox.html> |
| |
| 5. QUESTION: now if there is a default properties (i.e. |
| output_xml.properties has been loaded) but the expected properties file does |
| not exist a error message will be printed to System.err and the processing |
| will continuing using just the default properties (output_xml.properties) I |
| felt that this is the best behavior. |
| |
| (comment by sboag: I think it's better to |
| throw a runtime exception in this case. |
| but we can discuss this over time. For now |
| the patch was modified to do the runtime exception).<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor XSLTSchema.java |
| java/src/org/apache/xalan/stree SourceTreeHandler.java |
| java/src/org/apache/xalan/templates ElemForEach.java |
| ElemLiteralResult.java |
| java/src/org/apache/xalan/transformer QueuedSAXEvent.java |
| ResultTreeHandler.java TransformerImpl.java |
| java/src/org/apache/xml/utils BoolStack.java |
| java/src/org/apache/xpath XPathContext.java<br/><ref>Committer's log entry: </ref>This check-in contains a couple things that overlapped on my |
| system, so I'm checking them in together. |
| 1) Unfinished (in progress) implementation of TransformSnapshot mechanism, |
| which will hopefully allow a result ContentHandler to take a snapshot |
| at a given point, and the restart execution from that point at some |
| later time. For tooling support. |
| 2) Check to make sure SourceTreeHandler isn't being entered twice, |
| which is related to the cocoon bug from a couple of weeks ago. This |
| will just help diagnose such a problem in the future. |
| 3) Removed the error stack trace print from postExceptionFromThread. |
| 4) Report exception in SourceTreeHandler#endDocument after |
| the join, if we can determine that the posted exception won't be |
| caught elsewhere. |
| 5) removed some catches that simply rethrew the exception |
| (thanks to Patrick Moore <patrickm@rioport.com>). |
| See my note on 3/27/2001 to Patrick for more info |
| on the last two.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/27/2001<br/><ref>Added: </ref>java/src/org/apache/xalan/transformer TransformSnapshot.java |
| TransformSnapshotImpl.java<br/><ref>Committer's log entry: </ref>Unfinished (in progress) implementation of TransformSnapshot mechanism, |
| which will hopefully allow a result ContentHandler to take a snapshot |
| at a given point, and the restart execution from that point at some |
| later time. For tooling support.on the last two.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>03/29/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor |
| ProcessorStylesheetElement.java |
| ProcessorTemplateElem.java StylesheetHandler.java |
| XSLTElementDef.java XSLTElementProcessor.java |
| XSLTSchema.java<br/><ref>Committer's log entry: </ref>Try to catch element order and required element errors during stylesheet |
| object creation. This new code adds an order and a required field to |
| XSLElementDef objects where it is applicable.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>04/02/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>Fix bugzilla bug 1170. If we're trying an xsl:apply-imports at the top level |
| (ie there are no |
| imported stylesheets), we need to indicate that there is no matching template |
| and prevent and infinite recursion by using the built-in template.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>04/02/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/extensions MethodResolver.java<br/><ref>Committer's log entry: </ref>Code cleanup submitted by Art Welch <art_w@EASTPOINT.COM>.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>04/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils TreeWalker.java<br/><ref>Committer's log entry: </ref>Add locator support to TreeWalker<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>04/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer |
| QueuedStartElement.java<br/><ref>Committer's log entry: </ref>Small fix made for getCurrentNode.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>04/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils TreeWalker.java<br/><ref>Committer's log entry: </ref>Commented out extra call to getData()... this could be a big performance |
| improvement for some stylesheets.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>04/09/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer |
| TransformSnapshotImpl.java TransformerImpl.java<br/><ref>Committer's log entry: </ref>Additional support for tooling. Allow tools to take a snapshot of context and |
| restart execution at that point.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>04/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor |
| XSLTElementProcessor.java |
| java/src/org/apache/xalan/res XSLTErrorResources.java |
| java/src/org/apache/xalan/transformer |
| TransformSnapshotImpl.java TransformerImpl.java<br/><ref>Committer's log entry: </ref>Misc stuff left out from previous check in<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>04/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/functions FuncCurrent.java<br/><ref>Committer's log entry: </ref>Don't assume that the object returned by getSubContextList() is a |
| PredicatedNodeTest object.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>04/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor ProcessorInclude.java |
| TransformerFactoryImpl.java |
| java/src/org/apache/xalan/transformer |
| TransformerIdentityImpl.java |
| java/src/org/apache/xml/utils TreeWalker.java<br/><ref>Committer's log entry: </ref>Create new TreeWalker constructor that takes a systemId parameter. Change |
| TreeWalker to change fields in the locator and not set it for each node.<br/><br/></li><li><ref>Committed by </ref>curcuru@apache.org<ref> on </ref>04/17/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath XPath.java<br/><ref>Committer's log entry: </ref>Fix Bugzilla bug: |
| PR: 1106 |
| Submitted by: elharo@metalab.unc.edu<br/><br/></li><li><ref>Committed by </ref>curcuru@apache.org<ref> on </ref>04/18/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql QueryParameter.java |
| SQLExtensionError.java XConnection.java<br/><ref>Committer's log entry: </ref>Minor Javadoc updates (add @author name, remove declared but unthrown @throws)<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>04/18/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql Column.java |
| ColumnAttribute.java ColumnData.java |
| ColumnHeader.java Row.java RowSet.java |
| StreamableNode.java XConnection.java |
| XStatement.java<br/><ref>Committer's log entry: </ref>Support for Streamable Mode- John Gentilin<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>04/24/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/objects XObject.java<br/><ref>Committer's log entry: </ref>Resolve bugzilla bug 1015 |
| <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1015>. |
| Fix prevents null pointer exceptions when null non-XSLT arguments are |
| passed to an extension function.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>04/24/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/extensions MethodResolver.java<br/><ref>Committer's log entry: </ref>Resolve bugzilla bug 1015 |
| <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1015>. |
| Fix prevents null pointer exceptions when null non-XSLT arguments are |
| passed to an extension function.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>04/24/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor |
| TransformerFactoryImpl.java<br/><ref>Committer's log entry: </ref>Fix copy/paste error. Want to use TransformerFactoryImpl's class loader.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>04/24/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer |
| TransformSnapshotImpl.java<br/><ref>Committer's log entry: </ref>Keep a copy of current contextNodeList is there is one<br/><br/></li><li><ref>Committed by </ref>curcuru@apache.org<ref> on </ref>04/25/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/xslt EnvironmentCheck.java<br/><ref>Committer's log entry: </ref>Added checkDirForJars() which checks java.ext.dirs as well now<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>04/26/2001<br/><ref>Added: </ref>java/src/javax/xml/transform package.html |
| java/src/javax/xml/transform/dom package.html |
| java/src/javax/xml/transform/sax package.html |
| java/src/javax/xml/transform/stream package.html<br/><ref>Committer's log entry: </ref>Add package.html for each package in javax.xml.transform.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>04/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>Resolve bug 1496 <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1496> |
| where xsl:param statements were not being reset properly if the TransformerImpl |
| was reused.<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>04/27/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/stree DocImpl.java<br/><ref>Committer's log entry: </ref>Fix for #1561<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>04/29/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/functions FuncExtFunction.java<br/><ref>Committer's log entry: </ref>Resolve bugzilla bug 1373 |
| <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1373>. |
| Added code to support return of Integer or Long by an external function. |
| Code was contributed by Patrick Moore <patmoore@ieee.org>.<br/><br/></li><li><ref>Committed by </ref>costin@apache.org<ref> on </ref>05/03/2001<br/><ref>Modified: </ref>java/src/javax/xml/transform/stream StreamResult.java |
| StreamSource.java<br/><ref>Committer's log entry: </ref>Small fix to avoid file:////path that may fail on some JDK.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>05/04/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql package.html<br/><ref>Committer's log entry: </ref>Preliminary updates for John G's work.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>05/07/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>Check for a null contextNodeList before returning its clone<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>05/07/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/stree StreeDOMBuilder.java<br/><ref>Committer's log entry: </ref>Set the element's level correctly, before we process attributes.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>05/08/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer |
| TransformerIdentityImpl.java<br/><ref>Committer's log entry: </ref>Resolve bugzilla 1648 |
| (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1648). |
| TransformerIdentityImpl was improperly using an old LexicalHandler when |
| invoked for a second transform. |
| This bug only affects identity transforms with StreamResults. |
| Many thanks to John Keyes <johnkeyes@yahoo.com> for reporting this bug.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>05/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor XSLProcessorVersion.java<br/><ref>Committer's log entry: </ref>Updated version number to 2.1.0<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>05/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/res XSLTInfo.properties<br/><ref>Committer's log entry: </ref>Updated version number to 2.1.0<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>05/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/functions FuncExtFunction.java<br/><ref>Committer's log entry: </ref>Change submitted by Patrick Moore <patmoore@ieee.org> as part of bugzilla |
| 1373 (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1373). |
| Return value from extension function is now generalized so that all |
| derivatives of Number are now properly handled.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>05/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor XSLTSchema.java<br/><ref>Committer's log entry: </ref>Set the correct order of xsl:include elements<br/><br/></li><li><ref>Committed by </ref>johng@apache.org<ref> on </ref>05/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql Column.java |
| ColumnAttribute.java ColumnData.java |
| ColumnHeader.java ConnectionPool.java |
| DefaultConnectionPool.java ExtensionError.java |
| PooledConnection.java QueryParameter.java Row.java |
| RowSet.java SQLExtensionError.java |
| StreamableNode.java XConnection.java |
| XConnectionPoolManager.java XStatement.java |
| package.html<br/><ref>Committer's log entry: </ref>Updates Javadocs |
| Submitted by:John Gentilin mailto://johnglinux@eyecatching.com<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>05/14/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/xslt Process.java<br/><ref>Committer's log entry: </ref>Correct typo introduced in revision 1.30 causing problems with transforms on |
| Unix platforms.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>05/14/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemChoose.java<br/><ref>Committer's log entry: </ref>Correct bugzilla bug 1748 |
| <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1748>. |
| When evaluating xsl:when, the xsl:choose element was used to resolve |
| namespace prefixes instead of |
| the xsl:when element itself. This caused namespace prefixes defined on the |
| xsl:when to be ignored.<br/><br/></li><li><ref>Committed by </ref>costin@apache.org<ref> on </ref>05/15/2001<br/><ref>Modified: </ref>java/src/javax/xml/parsers DocumentBuilderFactory.java |
| SAXParserFactory.java |
| java/src/javax/xml/transform TransformerFactory.java<br/><ref>Committer's log entry: </ref>Use the context class loader if available. |
| |
| The implementation is based on ExtensionHandler, and it's needed in order |
| to work in certain environments ( like tomcat ).<br/><br/></li><li><ref>Committed by </ref>costin@apache.org<ref> on </ref>05/15/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/extensions ExtensionHandler.java |
| ExtensionHandlerGeneral.java<br/><ref>Committer's log entry: </ref>Make getClassForName a public method. There are few other places in xalan |
| where Class.forName is used, and this can create problems in some cases |
| where the Thread.getContextClassLoader should be used. |
| |
| getClassForName uses introspection to call getContextClassLoader |
| ( so it works in JDK1.1 ). |
| |
| In ExtensionHandlerGeneral, use the thread loader to find BSF ( it may be |
| possible that xalan is installed in CLASSPATH, but BSF is in a webapp ).<br/><br/></li><li><ref>Committed by </ref>costin@apache.org<ref> on </ref>05/15/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor |
| CompilingStylesheetHandler.java |
| java/src/org/apache/xalan/serialize SerializerFactory.java<br/><ref>Committer's log entry: </ref>2 more instances where Class.forName was used. |
| |
| Use the method in ExtensionHandler for consistency ( we could move it in |
| org.apache.xml.utils, but for now it's easier to just use it as it is )<br/><br/></li><li><ref>Committed by </ref>costin@apache.org<ref> on </ref>05/15/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/stree SourceTreeHandler.java |
| java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>This is the "thread pooling hook". |
| |
| It slightly changes the API used to create and wait for the transform thread. |
| Instead of using threadCreate() and Thread.start() that creates a new thread |
| and thread.join() that waits for a thread to end, we now use a |
| ThreadControler |
| class that has the equivalent methods: |
| - run( Runnable ) - executes a task in a thread. The default implementation |
| is identical with what we had, using new Thread() and start() |
| - waitTread() - waits for a task to end. The default impl. is identical with |
| the previous code, using thread.join(). |
| |
| Someone wanting to use a thread pool for xalan will have to extend |
| the ThreadControler and override the 2 methods, then call setThreadController. |
| |
| Xalan itself doesn't implement a thread pool right now ( for mosts uses it's |
| not even needed - if you just do few transforms for example ), instead |
| a server that runs xalan could plug it's own thread pool.<br/><br/></li><li><ref>Committed by </ref>Gary L Peskin <garyp@firstech.com><ref> on </ref>05/15/2001<br/><ref>Committer's log entry: </ref> |
| > Use the context class loader if available. |
| > |
| > The implementation is based on ExtensionHandler, and it's needed in order |
| > to work in certain environments ( like tomcat ). |
| > |
| ><br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>05/16/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql ExtensionError.java<br/><ref>Committer's log entry: </ref>Fixed "conflict" in javadoc comments.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>05/16/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql package.html<br/><ref>Committer's log entry: </ref>Editing pass.<br/><br/></li><li><ref>Committed by </ref>tmiller@apache.org<ref> on </ref>05/17/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/xsltc TransletOutputHandler.java<br/><ref>Committer's log entry: </ref>bug # 1406 fixed, omit xml header implemented<br/><br/></li><li><ref>Committed by </ref>curcuru@apache.org<ref> on </ref>05/17/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/xslt Process.java<br/><ref>Committer's log entry: </ref>Update Javadoc and remove commented out reference to properties file |
| PR:Bugzilla1627<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>05/18/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer ResultTreeHandler.java<br/><ref>Committer's log entry: </ref>Resolve bug 1330 <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1330>. |
| setContentHandler failed to also reset m_lexicalHandler if the ContentHandler |
| was also a LexicalHandler. This caused the old LexicalHandler to be used |
| which |
| was pointing to a previous result tree.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>05/18/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor |
| TransformerFactoryImpl.java<br/><ref>Committer's log entry: </ref>Resolve bug 1762 <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1762>. |
| TransformerFactoryImpl's URIResolver was not propagated to created |
| Transformers. |
| Modified code to propagate.<br/><br/></li><li><ref>Committed by </ref>curcuru@apache.org<ref> on </ref>05/19/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils TreeWalker.java |
| SystemIDResolver.java<br/><ref>Committer's log entry: </ref>Catch SecurityException whenever accessing System.getProperty("user.dir"); |
| minor javadoc update<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>05/21/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemCopy.java |
| ElemValueOf.java |
| java/src/org/apache/xalan/transformer TreeWalker2Result.java |
| java/src/org/apache/xpath/functions FuncLast.java<br/><ref>Committer's log entry: </ref>Fix for bugs reported by the Eclipse folks for TransformState, where |
| some operations (xsl:value-of, xsl-copy) were not pushing the |
| current node on the current node stack. Addresses |
| http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1524.<br/><br/></li><li><ref>Committed by </ref>curcuru@apache.org<ref> on </ref>05/21/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates OutputProperties.java<br/><ref>Committer's log entry: </ref>Catch SecurityException as needed |
| PR: Bugzilla1258<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>05/21/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates OutputProperties.java<br/><ref>Committer's log entry: </ref>Fix to the following bug reported by dims@yahoo.com: |
| |
| loadPropertiesFile method in org\apache\xalan\templates\OutputProperties.java |
| does not fall back |
| to the Thread Context Class Loader to load properties files like |
| output_xml.properties etc. This |
| is causing problems in ServletExec_3_1+C2.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>05/21/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates OutputProperties.java<br/><ref>Committer's log entry: </ref>Correct implementation of ContextClassLoader to support case where properties |
| file is to be loaded by a different ClassLoader than the OutputProperties |
| class. Thanks to Davanum Srinivas <dims@yahoo.com> for this code and for |
| reporting this bug. |
| loadPropertiesFile should eventually be moved into a thread-specific class.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>05/21/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor |
| TransformerFactoryImpl.java |
| java/src/org/apache/xalan/serialize CharInfo.java |
| java/src/org/apache/xpath/functions FuncSystemProperty.java<br/><ref>Committer's log entry: </ref>Modify getResourceAsStream calls to use the contextClassLoader, if available. |
| This is a temporary fix until we can centralize this function.<br/><br/></li></ul><note>This release includes no updates of the compatibility source code.</note> |
| </s3> |
| |
| <s3 title="Changes for &xslt4j; 2.0.1"> |
| <p>This release includes a number of bug fixes to the &xslt4j; and TrAX core and Xalan-Java 1 compability API. We have also</p> |
| <ul> |
| <li>Entered all known &xslt4j; 2 <link anchor="bugs">bugs</link> in the Apache Bugzilla database<br/><br/></li> |
| <li>Added support for using custom URIResolver, EntityResolver, and ContentHandler implementations with the <link |
| idref="commandline">command-line utility</link><br/><br/></li> |
| <li>Upgraded from Ant 1.2 to Ant 1.3 for our <link anchor="build">builds</link> (the new ant.jar is in the bin directory).</li> |
| </ul> |
| <p>Core source code updates:</p> |
| <ul> |
| <li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes ChildWalkerMultiStep.java<br/><ref>Committer's log entry: </ref>Fix for bug reported by "Chris P. McCabe" <chris_mccabe@choicehotels.com> |
| 02/06/2001 06:55 PM. |
| Defensive fix for if the last used walker is null, then don't check to |
| see if it is a fast walker! Without this, a null pointer exception is |
| very possible.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>Fixes for exceptions being thrown that weren't being passed through |
| the error listener.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/07/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes FollowingWalker.java<br/><ref>Committer's log entry: </ref>Fix for bug reported by Dave Haffner <dave.haffner@xmls.com> |
| 02/06/2001 04:03 AM |
| In parentNode(), don't screen out nextAncestor, since the parent |
| is never actually returned. This sets things up correctly for firstChild |
| and nextSibling.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/07/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes PrecedingWalker.java<br/><ref>Committer's log entry: </ref>Fix for bug reported by Dave Haffner <dave.haffner@xmls.com> |
| 02/06/2001 04:03 AM |
| In nextSibling(), don't return null if isAncestorOfRootContext, instead |
| do next.getFirstChild().<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/07/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath SourceTreeManager.java<br/><ref>Committer's log entry: </ref>Fix for bug reported by anders.domeij@uc.se |
| 02/07/2001 09:35 AM |
| removed extra bogus TransformerException decl in resolveURI<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/08/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/stree SourceTreeHandler.java<br/><ref>Committer's log entry: </ref>Fix bug reported by Jason Harrop <jharrop@bigpond.net.au> |
| 02/07/2001 08:12 PM |
| Don't process comment or whitespace events if inside a startDTD/endDTD |
| event.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/10/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/axes WalkerFactory.java<br/><ref>Committer's log entry: </ref>In indirect response to bug posted by "Thee Boon Hoo" <theebh@newstakes.com> |
| 02/07/2001 09:37 PM |
| |
| "//table[1]" patterns would give one node |
| when they should have given 2, when applied to Boon Hoo's |
| source. |
| "//table[1]" is equivelent to |
| "/descendant-or-self::node()/table[1]", |
| and so must return the first table child |
| of each table-inst element. |
| |
| An optimization was optimizing this to |
| "/descendant-or-self::table, which is |
| fine as long as indexing isn't used. Since |
| we can not tell until runtime if indexing |
| is being used, we have to turn of this |
| optimization for all predicated "//foo[xx]" |
| patterns.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/12/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor StylesheetPIHandler.java |
| TransformerFactoryImpl.java<br/><ref>Committer's log entry: </ref>Patch for Dmitri IIyin to use the specified URIResolver.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/12/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemNumber.java<br/><ref>Committer's log entry: </ref>Number Expression should be evaluated then rounded up.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/xslt Process.java<br/><ref>Committer's log entry: </ref>Create a document fragment for the output node, for -flavor d2d.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/compiler Compiler.java<br/><ref>Committer's log entry: </ref>Better error message when quo is used.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemCallTemplate.java |
| ElemChoose.java ElemCopy.java ElemFallback.java |
| ElemIf.java ElemLiteralResult.java |
| ElemTemplate.java |
| java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>Remove extra method/call to TransformerImpl.executeChildTemplates()<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/patterns NodeTest.java<br/><ref>Committer's log entry: </ref>Return an empty string instead of null from getLocalName() when the |
| nodetest does not have a name. Encountered with the SQL extension, |
| in response to bug reported by "Michael Kay" <mhkay@iclway.co.uk>, |
| 02/08/2001 08:57 AM.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql ColumnData.java<br/><ref>Committer's log entry: </ref>In getData() return an empty string instead of null if there is |
| no data to be obtained. |
| In response to bug reported by "Michael Kay" <mhkay@iclway.co.uk>, |
| 02/08/2001 08:57 AM.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>02/19/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/extensions MethodResolver.java<br/><ref>Committer's log entry: </ref>Correct ConversionInfo array for Node-Set and RTF. Remove DocumentFragment |
| from RTF and replace with NodeList. Remove duplicate Boolean from both. Fix |
| Boolean conversion to make java.lang.Boolean higher than string.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/19/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql ColumnHeader.java |
| RowSet.java XStatement.java<br/><ref>Committer's log entry: </ref>Use null nodetest to mean the same as "node()". This fixes a bug reported |
| by "Voytenko, Dimitry" <DVoytenko@SECTORBASE.COM> |
| where <xsl:copy-of select="sql:query(...)"/> |
| crashes with NullPointerException, i.e. |
| there are cases where we really don't want |
| to set the NodeTest.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/20/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/compiler XPathParser.java<br/><ref>Committer's log entry: </ref>Check for null token before checking if it is a letter<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/20/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer |
| TransformerIdentityImpl.java<br/><ref>Committer's log entry: </ref>Fix made for bug reported by "Glencross, Christian" |
| <Christian.Glencross@gs.com> |
| on 02/16/2001 10:18 AM. |
| Xerces 1.2.3 SAX parser calls |
| handler.setDocumentLocator() before handler.startDocument(). |
| TransformerIdentityImpl.m_resultContentHandler isn't initialised until |
| TransformerIdentityImpl.startDocument() is called. |
| Added lazy construction of result handler |
| in setDocumentLocator, in addition to |
| startDocument.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>02/21/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib Extensions.java<br/><ref>Committer's log entry: </ref>Correct implementation of string value of a node.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>02/21/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql Column.java |
| ColumnAttribute.java ColumnData.java |
| ColumnHeader.java Row.java RowSet.java |
| StreamableNode.java XConnection.java |
| XStatement.java package.html<br/><ref>Committer's log entry: </ref>Added experimental usage metatag to all classes in this package, |
| and an explanatory note to package.html.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/22/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/stree ElementImpl.java<br/><ref>Committer's log entry: </ref>Bug fix attributed to Norman Walsh <ndw@nwalsh.com>, on |
| 02/20/2001 09:50 AM. if the attribute 'name' doesn't occur in the AttList, |
| the |
| result of getIndex(name) is -1, but |
| getChildAttribute() would incorrectly |
| return the first attribute. Fix returns |
| null if index < 0.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/22/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/serialize SerializerToXML.java |
| java/src/org/apache/xalan/transformer |
| TransformerIdentityImpl.java<br/><ref>Committer's log entry: </ref>Implement DeclHandler for identity transforms<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>02/22/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>Fix for bug originally reported by Daryl Beattie <DarylB@screamingmedia.com> |
| on 02/14/2001 04:16 PM. A hang was occuring inside the use |
| of a Result Tree Fragment. When the result tree fragement was |
| being created, the Redirect extension was being called, which |
| called createResultContentHandler which set the ContentHandler |
| in the Transformer, but not in the ResultTreeHandler. Then, Redirect |
| called Transformer#executeChildTemplates( |
| ElemTemplateElement elem, Node sourceNode, QName mode, |
| ContentHandler handler) |
| which saves the reference to the original content handler in |
| the transformer, and then sets the new one by calling setContentHandler, |
| which sets the ContentHandler in the ResultTreeHandler as well |
| as the Transformer. When it tried to restore the old ContentHandler, |
| it restored the value in the ResultTreeHandler to a Serializer, instead |
| of the correct ContentHandler. When transformToRTF then called |
| endDocument on it's resultTreeFragment, the event was sent |
| to the Serializer instead of the SourceTreeHandler, and thus the |
| isComplete flag was not set, and thus the hang. (whew!) |
| The fix is in executeChildTemplates save the value of the |
| resultTreeHandler's contentHandler as well as Transformer's |
| content handler, and restore them both. A more architectual fix |
| could be made, but not without high risk, so I think this is the best |
| and safest way to fix it.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>02/23/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/res XSLTInfo.properties<br/><ref>Committer's log entry: </ref>Changed version to 2.0.1<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>02/23/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor XSLProcessorVersion.java<br/><ref>Committer's log entry: </ref>Changed version to 2.0.1<br/><br/></li><li><ref>Committed by </ref>curcuru@apache.org<ref> on </ref>02/28/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/res XSLTErrorResources.java<br/><ref>Committer's log entry: </ref>Update text of error messages |
| Submitted by: Andreas Zehnpfund<br/><br/></li><li><ref>Committed by </ref>curcuru@apache.org<ref> on </ref>02/28/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/xslt Process.java<br/><ref>Committer's log entry: </ref>Update printArgOptions() with better text and to better reflect actual |
| options that are currently supported; catch missing -IN argument<br/><br/></li><li><ref>Committed by </ref>jkesselm@apache.org<ref> on </ref>03/05/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/client XSLTProcessorApplet.java |
| java/src/org/apache/xalan/processor StylesheetHandler.java |
| TransformerFactoryImpl.java |
| java/src/org/apache/xalan/stree DocImpl.java |
| StreeDOMBuilder.java TextImpl.java |
| java/src/org/apache/xalan/templates OutputProperties.java |
| java/src/org/apache/xalan/xslt Process.java |
| java/src/org/apache/xml/utils FastStringBuffer.java |
| java/src/trax trax.properties<br/><ref>Committer's log entry: </ref>New approach to FastStringBuffer, and changes needed to support it. |
| We still need to do some serious work on both the initial values of the |
| tuning parameters and the heuristics driving the "chunk growth" algorithms. |
| Currently set for fixed-sized chunks of 8Kch in main tree, .5Kch in RTF.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemElement.java |
| ElemForEach.java ElemLiteralResult.java |
| java/src/org/apache/xalan/transformer |
| ClonerToResultTree.java QueuedSAXEvent.java |
| QueuedStartDocument.java QueuedStartElement.java |
| ResultTreeHandler.java TransformerImpl.java |
| TreeWalker2Result.java<br/><ref>Committer's log entry: </ref>Fix for http://nagoya.apache.org/bugzilla/show_bug.cgi?id=741. |
| |
| 1) ResultTreeHandler now implements the TransformState interface. |
| 2) Queued state such as the current node and the current template is stored |
| as part of QueuedStartElement. Storage will only occur if the ContentHandler |
| implements TransformClient. |
| 3) When state is requested (for instance TransformState#getCurrentElement()), |
| if the queued element is null or not pending (for instance, in a characters |
| event), it will get the state from the transformer, otherwise it will get the |
| state from the queued element. |
| |
| Other fixes were attempted for this problem, including trying to |
| get rid of queueing altogether, and flushing a bit earlier before |
| the state was pushed on the various stacks, but both of |
| these had show-stopping issues (see discussions |
| on xalan-dev). |
| |
| Note that for the moment the ContextNodeList is node |
| cloned as it needs to be in order for |
| TransformState#getContextNodeList.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>03/06/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemParam.java |
| java/src/org/apache/xpath Arg.java VariableStack.java<br/><ref>Committer's log entry: </ref>The field Arg.isParamVar was attempting to serve two functions: to indicate |
| variable Frame entries which are not currently activated and to indicate Frames |
| containing parameters passed with xsl:with-param. When processing was finished |
| for a node in a node-set, the isParamVar flag was turned on to indicate the |
| Frame slot was available. Unfortunately, this also indicated that the item was |
| passed as a parameter which it wasn't. This fix changes isParamVar into to |
| fields, isAvailable which indicates that the slot is available and |
| isFromWithParam indicating the Frame slot came from an xsl:with-param or a |
| top-level parameter passed in via the tranformerImpl.setParameter() API. |
| I have tested this change against the conformance suite and had no |
| regression. I've also submitted a test case which fails on the existing |
| codebase but works okay after this fix. |
| It is possible that I've missed something with regard to the API setParameter |
| calls but we can fix those if problems are reported.<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>03/07/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils FastStringBuffer.java<br/><ref>Committer's log entry: </ref>Correct operation when length of content to be appended is zero.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>03/07/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/serialize SerializerToXML.java<br/><ref>Committer's log entry: </ref>Fix closing out doctype declaration<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>03/08/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils SystemIDResolver.java<br/><ref>Committer's log entry: </ref>Change SystemIdResolver to default to user.dir if the base URI is null<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>03/09/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java |
| java/src/org/apache/xpath VariableStack.java<br/><ref>Committer's log entry: </ref>Parameters set with setParameter were available to stylesheet as variable |
| references ($myParam) even though there was no xsl:param element to receive it.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>03/09/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer |
| TransformerIdentityImpl.java<br/><ref>Committer's log entry: </ref>Check if there is a DeclHandler before calling it.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils WrappedRuntimeException.java<br/><ref>Committer's log entry: </ref>Patch attributed to Patrick Moore <patrickm@rioport.com> on 03/09/2001. |
| Adds another constructor to pass in the error message.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemAttribute.java |
| ElemElement.java<br/><ref>Committer's log entry: </ref>Checkin addresses http://nagoya.apache.org/bugzilla/show_bug.cgi?id=923. |
| elemAttribute now derives from elemElement so the basic name resolution |
| code can be shared. Breaks attribset24 test, but I think the newer |
| behavior is better. New virtual methods overloaded by elemAttribute are |
| constructNode, resolvePrefix, and validateNodeName. Also, in the |
| elemAttribute#execute method, checks are made to make sure an |
| element is pending.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils SystemIDResolver.java<br/><ref>Committer's log entry: </ref>Added getAbsoluteURI(String url), and merge |
| with Myriam's changes. |
| Part of fix for problem found when |
| investigating http://nagoya.apache.org/bugzilla/show_bug.cgi?id=906.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor |
| TransformerFactoryImpl.java<br/><ref>Committer's log entry: </ref>Call getAbsoluteURI(String url) for the source URL. |
| Fix for problem found when |
| investigating http://nagoya.apache.org/bugzilla/show_bug.cgi?id=906. |
| This tries to force us always having an absolute URL in the processing |
| stack as the base URL, which should be OK, I hope.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer TransformerImpl.java<br/><ref>Committer's log entry: </ref>Call getAbsoluteURI(String url) for the source URL. |
| Fix for problem found when |
| investigating http://nagoya.apache.org/bugzilla/show_bug.cgi?id=906. |
| This tries to force us always having an absolute URL in the processing |
| stack as the base URL, which should be OK, I hope.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/transformer QueuedEvents.java |
| QueuedStartElement.java ResultTreeHandler.java<br/><ref>Committer's log entry: </ref>The user for http://nagoya.apache.org/bugzilla/show_bug.cgi?id=741 reported |
| problems on testing, so these changes are a re-fix. He tested and |
| everything seems OK now. There actually may be a slight performance |
| improvement involved here.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/serialize SerializerToHTML.java<br/><ref>Committer's log entry: </ref>Applied patches from dmitri.ilyin@memiq.com (Dmitri Ilyin) |
| from http://nagoya.apache.org/bugzilla/show_bug.cgi?id=705.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath XPathAPI.java<br/><ref>Committer's log entry: </ref>Applied patch submitted by nboyd@atg.com (Norris Boyd) |
| at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=702.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/serialize Encodings.java<br/><ref>Committer's log entry: </ref>Applied patch submitted by havardw@underdusken.no (H嶡rd Wigtil). |
| Also added "XXX-X" variants for all "XXX_X" java encoding names. |
| I'm not totally confident that this is the right thing to do, but I can't |
| see that it will hurt, except to make the table a bit larger. I |
| would prefer to be safe and make sure we handle the encoding. |
| See my comments in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=718.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates ElemTemplateElement.java |
| StylesheetRoot.java<br/><ref>Committer's log entry: </ref>Minor changes to better bottleneck throwing of Runtime exceptions |
| during processing.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor |
| TransformerFactoryImpl.java<br/><ref>Committer's log entry: </ref>Catch all exceptions thrown when processing stylesheet, and send |
| them to the error listener. There's probably some danger of having |
| the same error sent to the error listener multiple times, but better too |
| many reports, than none, I guess. |
| This addresses http://nagoya.apache.org/bugzilla/show_bug.cgi?id=906.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql XConnection.java |
| XStatement.java<br/><ref>Added: </ref>java/src/org/apache/xalan/lib/sql ConnectionPool.java |
| DefaultConnectionPool.java ExtensionError.java |
| PooledConnection.java QueryParameter.java |
| SQLExtensionError.java XConnectionPoolManager.java<br/><ref>Committer's log entry: </ref>These are John Gentilin <johnglinux@eyecatching.com> |
| patches for connection pooling and parameterized |
| queries. These should be considered to be unstable |
| right now, as we are still working on some things.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/11/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor ProcessorInclude.java |
| TransformerFactoryImpl.java |
| java/src/org/apache/xalan/serialize SerializerToXML.java |
| java/src/org/apache/xalan/stree StreeDOMHelper.java |
| java/src/org/apache/xalan/transformer ResultTreeHandler.java |
| TransformerIdentityImpl.java TreeWalker2Result.java |
| java/src/org/apache/xml/utils AttList.java TreeWalker.java |
| java/src/org/apache/xpath DOM2Helper.java XPathContext.java<br/><ref>Committer's log entry: </ref>The DOM2Helper#isNodeAfter(Node node1, Node node2) method |
| has been fixed so that it no longer does the try/catch thing if one |
| of the nodes doesn't implement DOMOrder, but instead does an |
| instanceof test. In StreeDOMHelper, it overloads this method and |
| *does* do the try/catch business, since almost always both nodes |
| will implement DOMOrder in this case, and this will be faster than |
| an instanceof test. Also, in various classes, I did some stuff to try |
| and make sure that a DOM2Helper wasn't being created and used |
| when a StreeDOMHelper is needed. |
| |
| This addresses http://nagoya.apache.org/bugzilla/show_bug.cgi?id=800 |
| and should give a good performance fix for foreign DOM processing.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/12/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath/patterns NodeTest.java<br/><ref>Committer's log entry: </ref>Xerces at some point decided to use "" instead |
| of null for null namespaces. There has been a |
| discussion between Gary Peskin in |
| Joe Kessleman on xalan-dev about this, |
| but I hadn't been fully keeping up the the |
| thread that well, and missed it's relation to |
| this problem. I include some of the discussion |
| at the end of this note. I made Xalan be able to |
| compare a "" namespace to null for now, until |
| we get this resolved. |
| |
| The gist of the discussion on xalan-dev regarding this is: |
| |
| >>1. Declare the Xerces-J support of schemas to have a bug and ask that |
| >>Xerces be corrected to always use a null namespace URI to indicate that |
| >>there is no default namespace. Even if the Xerces people change this |
| >>behavior, is this correct? |
| > |
| > Yes. If your description of the problem is accurate (you should probably |
| > submit a more detailed case so it can be reproduced in the lab), this is a |
| > parser/DOM-builder bug.<br/><br/></li><li><ref>Committed by </ref>costin@apache.org<ref> on </ref>03/12/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql ExtensionError.java<br/><ref>Committer's log entry: </ref>Removed ( commented out ) dump() method and the imports in ExtensionError. |
| |
| So far the method doesn't seem to be used ( no warning in the compile ). |
| |
| The problem is that this method is breaking the build with crimson ( since |
| it uses xerces-specific classes ). It is possible to implement it on top |
| of the serialization classes that are part of xalan - if someone needs the |
| method I'll try to port it.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils TreeWalker.java<br/><ref>Committer's log entry: </ref>Added back in the TreeWalker(ContentHandler contentHandler) |
| constructor, because I'm worried I'll break more dependent code.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>03/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/res XSLTErrorResources.java |
| java/src/org/apache/xalan/xslt Process.java<br/><ref>Committer's log entry: </ref>Implement new arguments for the command line interface: URIResolver, |
| EntityResolver and ContentHandler<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>03/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/templates FuncFormatNumb.java<br/><ref>Committer's log entry: </ref>Fix error message to say that 2 or 3 arguments are required.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>03/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/processor ProcessorLRE.java |
| java/src/org/apache/xalan/res XSLTErrorResources.java<br/><ref>Committer's log entry: </ref>Better error message for missing or incorrect XSLT namespace declaration in a |
| stylesheet<br/><br/></li><li><ref>Committed by </ref>garyp@apache.org<ref> on </ref>03/13/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib Redirect.java |
| java/src/org/apache/xalan/transformer TransformerImpl.java |
| java/src/org/apache/xalan/xslt Process.java<br/><ref>Committer's log entry: </ref>Remember the Result that was used to trigger the transform. Access that |
| result from the Redirect extension to make file references in Redirect relative |
| to the original result URI. |
| If this is not available, references are relative to the source URI.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/14/2001<br/><ref>Modified: </ref>java/src/org/apache/xpath VariableStack.java<br/><ref>Committer's log entry: </ref>Added protection for null pointer exception that I discovered when |
| running some Cocoon tests. Since I've never seen this before, |
| I assume this is related to the changes that Gary made, but am |
| unsure as it's 4:00 in the morning and I'm too tired to look into it deeply.<br/><br/></li><li><ref>Committed by </ref>curcuru@apache.org<ref> on </ref>03/14/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/xslt Process.java<br/><ref>Committer's log entry: </ref>Remove check for missing -IN arg; there are a number of use |
| cases for calling Process.main without an XML document<br/><br/></li><li><ref>Committed by </ref>costin@apache.org<ref> on </ref>03/14/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/xslt Process.java<br/><ref>Committer's log entry: </ref>A (last ? ) place where XMLReaderFactory was used without |
| trying jaxp first. I used the same code that is used in all other |
| places in xalan. |
| |
| With this change, the parser defined in XSLTInfo.properties will be used |
| only if jaxp is not available.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>03/14/2001<br/><ref>Modified: </ref>java/src/org/apache/xml/utils StringVector.java<br/><ref>Committer's log entry: </ref>Added missing @serial Javadoc tags.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/15/2001<br/><ref>Modified: </ref>java/src/org/apache/xalan/lib/sql ConnectionPool.java |
| DefaultConnectionPool.java ExtensionError.java |
| SQLExtensionError.java XConnection.java |
| XConnectionPoolManager.java XStatement.java<br/><ref>Committer's log entry: </ref>Update from John Gentilin <johnglinux@eyecatching.com> to |
| fix connection cleanup.<br/><br/></li></ul><p>Compatibility source code updates:</p><ul><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/02/2001<br/><ref>Modified: </ref>java/compat_src/org/apache/xalan/xslt XSLTInputSource.java |
| XSLTResultTarget.java<br/><ref>Committer's log entry: </ref>Implement some more methods for compatibility<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>02/02/2001<br/><ref>Modified: </ref>java/compat_src/org/apache/xalan/xslt XSLTInputSource.java<br/><ref>Committer's log entry: </ref>Fixed javadoc for api that was just added back.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>02/02/2001<br/><ref>Modified: </ref>java/compat_src/org/apache/xalan/xslt XSLTResultTarget.java<br/><ref>Committer's log entry: </ref>Fixed javadoc for api that was just added back.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/02/2001<br/><ref>Modified: </ref>java/compat_src/org/apache/xalan/xslt XSLTEngineImpl.java<br/><ref>Committer's log entry: </ref>Fix problem with calling the processor with a liaison<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/02/2001<br/><ref>Modified: </ref>java/compat_src/org/apache/xalan/xslt XSLTEngineImpl.java<br/><ref>Committer's log entry: </ref>Fix problem where source file was being parsed more than once and if using an |
| input stream, we would get a read error<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/12/2001<br/><ref>Modified: </ref>java/compat_src/org/apache/xalan/xslt XSLTEngineImpl.java<br/><ref>Committer's log entry: </ref>Set system id in stylesheet handler<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/14/2001<br/><ref>Modified: </ref>java/compat_src/org/apache/xalan/xslt XSLTInputSource.java<br/><ref>Committer's log entry: </ref>Call local setSystemId.<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/15/2001<br/><ref>Modified: </ref>java/compat_src/org/apache/xalan/xslt XSLTEngineImpl.java<br/><ref>Committer's log entry: </ref>Fix problem with processing an input source created from a reader with no |
| systemId |
| Fix problem with reading an input source file twice if it has a PI<br/><br/></li><li><ref>Committed by </ref>mmidy@apache.org<ref> on </ref>02/22/2001<br/><ref>Modified: </ref>java/compat_src/org/apache/xalan/xslt StylesheetRoot.java<br/><ref>Committer's log entry: </ref>Add getOutputMethod API.<br/><br/></li><li><ref>Committed by </ref>dleslie@apache.org<ref> on </ref>03/07/2001<br/><ref>Modified: </ref>java/compat_src/org/apache/xalan/xpath/xml |
| XMLParserLiaisonDefault.java<br/><ref>Committer's log entry: </ref>Put in Apache copyright.<br/><br/></li><li><ref>Committed by </ref>sboag@apache.org<ref> on </ref>03/13/2001<br/><ref>Modified: </ref>java/compat_src/org/apache/xalan/xpath/xml TreeWalker.java |
| java/compat_src/org/apache/xalan/xslt XSLTEngineImpl.java<br/><ref>Committer's log entry: </ref>Made changes for change to API for XalanJ2 TreeWalker, which |
| now requires that the DOM helper be created by the caller.</li> |
| </ul> |
| </s3> |
| |
| <s3 title="Changes for &xslt4j; version 2.0.0"> |
| <p>Release 2.0 includes several bug fixes to the &xslt4j; and TrAX core and to the Xalan-Java 1 compatibility API. We also updated bsf.jar to the <resource-ref idref="bsf"/> release candidate 2.2, which fixes a bug running JPython extensions.</p> |
| <p><em>Core bug fixes:</em></p> |
| <ul> |
| <li>A threading problem showed up when using multiple processors. We fixed it by using a separate XPathContext object to do whitespace node |
| matches (xsl:strip-space).<br/><br/></li> |
| <li>Fixed a bug running Norm Walsh's DocBook stylesheets by not setting the variable stack position if the FilterExprWalker is not owned by a |
| top-level NodeIterator.<br/><br/></li> |
| <li>Fixed a problem with null namespace being passed from xsl:element. This bug also surfaced while processing DocBook |
| stylesheets.<br/><br/></li> |
| <li>In the interest of stability, we now treat "unknown error in XPath" as a fatal error.<br/><br/></li> |
| <li>Added support in stylesheet processing instructions for "text/xml" and "application/xml+xslt" mime types.<br/><br/></li> |
| <li>Fixed tokenizing of stylesheet processing instructions to allow parameters to be passed to server in href attributes.<br/><br/></li> |
| <li>Fixed a bug passing Transformer creation error messages to ErrorListener when an ErrorListener has been set on |
| TransformerFactory.<br/><br/></li> |
| <li>When using an Exception to instantiate a FactoryConfigurationError (extends Error), we now propagate the Exception message to |
| super().<br/><br/></li> |
| <li>Added defensive code to ElemTemplateElement for handling a null URI.<br/><br/></li> |
| <li>When using an Exception to instantiate a TransformerException (extends Exception), we now propagate the Exception message to super() |
| rather than a generic message.<br/><br/></li> |
| <li>Fixed a bug (the generation of an unwanted entity reference) performing the identity transformation |
| (see <link idref="usagepatterns" anchor="serialize">Serializing output</link>) with an XML document containing a DOCTYPE |
| declaration.<br/><br/></li> |
| <li>Message manager modified so that the SourceLocator must always be passed in, |
| which will make a major difference in getting line number information.<br/><br/></li> |
| <li>xsl:element's handling of namespace attribute and prefix in |
| name attribute changed so that it no longer manufactures prefixes... |
| it always tries its best to match the prefix entered.<br/><br/></li> |
| <li>Bug fixed with namespace contexts in the stylesheet processor. |
| The bug could cause <a xmlns:a="x"><b> to produce <a xmlns:a="x"><b xmlns:a="x">.<br/><br/></li> |
| <li>Modified processing of xsl:message to enhance it as a debugging aid. Line numbers are now output with each |
| message. If the terminate attribute is true (the default is false) the message is sent to the console, and an exception is thrown with the |
| message "Stylesheet directed termination".<br/><br/></li> |
| <li>In TransformerException, check that the cause != null when checking for a contained exception.<br/><br/></li> |
| <li>Fixed a problem validating non-namespaced attributes and a problem allowing non-namespaced attributes to be children of the |
| stylesheet element.<br/><br/></li> |
| <li>Fixed checking of number of arguments in document() function.<br/><br/></li> |
| <li>Fixed problem with mutation of templates at run time. Templates resolution now takes place during the compose() method.<br/><br/></li> |
| <li>Fixed some minor threading issues in org.apache.xalan.stree (Child, Parent, ElementImpl, SourceTreeHandler).<br/><br/></li> |
| <li>Synchronized TrAX API functions subject to mutation to prevent mutation during a transformation.<br/><br/></li> |
| <li>Fixed bug reported by Jano Elovirta: substring() was returning an error if the start index is larger than the string.<br/><br/></li> |
| <li>Set StringKey.toString() to return the underlying String (m_str), thus avoiding a potential symmetry problem with the equals() method |
| reported by Ito Kazumitsu.<br/><br/></li> |
| <li>In response to note from Ito Kazumitsu, changed Java encoding name "EUCJIS" in FormatterToXML to "EUC_JP".<br/><br/></li> |
| <li>When Xalan creates a FileOutputStream, it now closes the stream before exiting.<br/><br/></li> |
| <li>Fixed handling of an exception that can be thrown while building a DOM.<br/><br/></li> |
| <li>Fixed a problem reported by Dimitry Voytenko serializing compiled stylesheets.<br/><br/></li> |
| <li>For support of applets, modified TransformerFactory System.getProperty() calls to catch SecurityExceptions.<br/><br/></li> |
| <li>Fixed a bug reported by Krishna Mohan Meduri setting output properties.<br/><br/></li> |
| <li>Fixed error recovery when xsl:element encounters a bad name or unresolvable prefix.<br/><br/></li> |
| <li>Added AbstractMethodError handling to existing NoSuchMethodError handling as a fallback to the XMLReaderFactory for XML parsers that do |
| not implement the JAXP parsers interface for creating an XMLReader<br/><br/></li> |
| <li>Fixed bug with cloned iterators reported by Tim Sean.<br/><br/></li> |
| <li>Fixed null pointer exception that could occur with getValue("xxx").<br/><br/></li> |
| <li>Fixed bug reported by Tim Sean handling the xml:space attribute.</li> |
| </ul> |
| <p><em>Bug fixes in the <link idref="usagepatterns" anchor="compat">Xalan-Java 1 compatibility API</link>:</em></p> |
| <ul> |
| <li>Fixed ProblemListener (for processing error messages) to derive from &xslt4j; 2 ErrorHandler.<br/><br/></li> |
| <li>Fixed evaluation of stylesheet string parameters to conform to &xslt4j; 1 behavior (expressions for &xslt4j; 1 vs. String objects |
| for &xslt4j; 2).<br/><br/></li> |
| <li>Added XPathSupport and XPathSupportDefault, and fixed the derivation of XObject sub-types (XString, etc.).<br/><br/></li> |
| <li>Fixed bug with XSLTProcessor process(xmlIn, null, out) method so that it uses the StylesheetRoot (if one exists) that has been created |
| with the processStylesheet() method.</li> |
| </ul> |
| <p>For a list of tasks in the &xslt4j2; To-Do list that have been completed, see <jump href="todo.html#release-date-completed">Tasks completed</jump>.</p> |
| </s3> |
| |
| <s3 title="Changes for &xslt4j; version 2.0.D07"> |
| <p>&xslt4j; 2.0.D07 incorporates a <link idref="usagepatterns" anchor="compat">Xalan-Java 1 compatibility jar</link>, some performance enhancements, and a number of bug fixes for bugs found in version 2.0.D06.</p> |
| <ul> |
| <li>Fixed handling of disable-output-escaping="no". Previously, once it was turned on, it could not be turned off.<br/><br/></li> |
| <li>Fixed a bug with whitespace handling where Xalan was incorrectly checking for whitespace |
| stripping before collation of multiple whitespace events into a single text node.<br/><br/></li> |
| <li>Whitespace stripping wasn't working with input DOMs before. This is now fixed.<br/><br/></li> |
| <li>Fixed many exception handling problems and problems with error reporting.<br/><br/></li> |
| <li>Fixed a bug resetting parameters in Transformer clearParameters().<br/><br/></li> |
| <li>Fixed a bug where CDATA sections were not matching the text() node test.<br/><br/></li> |
| <li>Made better memory allocation problem with result tree fragments.<br/><br/></li> |
| <li>Made result tree fragment parsing of numbers consistent with strings.<br/><br/></li> |
| <li>Exceptions thrown from extensions should now be properly reported via the error listener.<br/><br/></li> |
| <li>Fixed hard-coded stack dump set off by m_reportInPostExceptionFromThread variable.<br/><br/></li> |
| <li>Fixed intermittent threading problem with text nodes being dropped.<br/><br/></li> |
| <li>Fixed problem with variable evaluation inside of union expressions.</li> |
| </ul> |
| </s3> |
| <s3 title="Changes for &xslt4j; version 2.0.D06"> |
| <p>We have fixed the bugs reported in &xslt4j; 2.0.D05. Along with several other enhancements, |
| we have also fixed a number of bugs found by testing and our users:</p> |
| <ul> |
| <li>Fixed some threading problems and improved support for handling Exceptions thrown in a secondary thread.<br/><br/> |
| Note: To support incremental output, &xslt4j; performs the transformation in a second thread while building the source tree in the main thread.<br/><br/></li> |
| <li>Fixed problems encountered in piping (utilizing transformation output as input for another transformation).<br/><br/></li> |
| <li>Fixed problems handling attributes and adding attributes to result tree.<br/><br/></li> |
| <li>Added defensive checking for null entities, null namespaces, and empty strings passed in for URIs and local names.<br/><br/></li> |
| <li>We now conform to the SAX convention of representing null namespaces with empty strings.<br/><br/></li> |
| <li>Fixed a bug encountered evaluating a variable in a predicate expression applied to child nodes.<br/><br/></li> |
| <li>Changed names of serializers from FormatterTo<ref>Xxx</ref> to SerializerTo<ref>Xxx</ref>. See |
| <jump href="apidocs/org/apache/xalan/serialize/package-summary.html">Package org.apache.xalan.serialize</jump>.<br/><br/></li> |
| <li>Improved debugging support in a number of areas.</li> |
| </ul> |
| </s3> |
| <s3 title="Changes for &xslt4j; version 2.0.D05"> |
| <p>All of the bugs reported in &xslt4j; 2.0.D01 have been fixed. The remainder of this section discusses two changes that we believe are of particular importance:</p> |
| <p><em>TrAX</em></p> |
| <p>The Transformation API for XML (TrAX) that &xslt4j2; implements has undergone substantial revisions since the release of &xslt4j; 2.0.D01. TrAX has joined the Java API for XML Parsing (JAXP) as part of the Sun® <resource-ref idref="jsr063"/>. Accordingly, the TrAX package names have changed. The conceptual organization has also changed somewhat: The primary transformation interfaces are defined in javax.xml.transform, with concrete classes for managing stream input/output, SAX parsers and ContentHandler, and DOM parsers and DOM trees in javax.xml.transform.stream, javax.xml.transform.sax, and javax.xml.transform.dom. For more information, see <link idref="trax">TRaX (Transformation API for XML)</link>, and review <link idref="usagepatterns">Usage Patterns</link>.</p> |
| <anchor name="outputprops"/><p><em>Output properties</em></p> |
| <p>The handling of xsl:output properties has changed: org.apache.xalan.serialize.OutputFormat and apache.xalan.templates.OutputFormatExtended were removed and replaced with org.apache.xalan.templates.OutputProperties. The SerializerFactory getSerializer() method now takes Properties rather than a String indicating the output method. You can replace <code>getSerializer("xml")</code>, for example, with <code>getSerializer(OutputProperties.getDefaultMethodProperties("xml"))</code>.</p> |
| <p>HTML, XML, and text xsl:output properties are specified in property files in org.apache.xalan.templates: output_html.properties, output_xml.properties, and output_text.properties.</p> |
| <p>You can start using the output properties defined in these files in your stylesheets. For example, you can turn URL escaping off in HTML output with<br/><code>{http\u003a//xml.apache.org/xslt}use-url-escaping=no</code><br/> |
| and you can control indenting with<br/> |
| <code>{http\u003a//xml.apache.org/xslt}indent-amount=<ref>n</ref></code></p> |
| <note>The colon after the "http" protocol must be escaped.</note> |
| <p>Character-to-entity mapping is specified in org.apache.xalan.serialize: HTMLEntities.res and XMLEntities.res. You can override entity ref |
| mapping from a stylesheet. For example:</p> |
| <source><?xml version="1.0"?> |
| <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" |
| xmlns:xalan="http://xml.apache.org/xslt" version="1.0"> |
| |
| <xsl:output xalan:entities="myentities.ent"/> |
| |
| <xsl:template match="/"> |
| <out>&#125;</out> |
| </xsl:template> |
| |
| </xsl:stylesheet></source> |
| <p>=== myentities.ent ===</p> |
| <source>quot 34 |
| amp 38 |
| lt 60 |
| gt 62 |
| lala 125</source> |
| <p>The output is:</p> |
| <source><?xml version="1.0" encoding="UTF-8"?> |
| <out>&lala;</out></source> |
| <p>See also <link idref="usagepatterns" anchor="outputprops">Setting output properties in your stylesheets</link>.</p> |
| </s3> |