XCLTC 1: Things To Do

See a list of developers/initials.

Planned releases:
00/00/00 Completed

For release: 00/00/00 , beta
Goal [conformance]: XSLT 1.0 compliant 100%.
Goal [performance]: Maintain current level.
Goal [stability]: Stable, reasonable.
Goal [api]: API Complete.
Goal [documentation]: Documentation functionally complete.

1) Replace all Project X components and APIs with JAXP equivalents (this includes updating compiler's parser to use SAX2/DOM2).
context: code, packages: org.apache.xalan.xsltc, category: feature, who: MJ, TM, priority: high

2) Produce documentation on architecture of XSLTC so the larger developer community can contribute to the development of XSLT.
context: doc, category: documentation, who: MJ, priority: high

3) Integrate tests not already there into the Xalan test suite and begin using the Xalan test suite to test XSLTC as a component of XalanJ2. (This should wait until #1 is done.)
context: test, packages:org.apache.xalan.xsltc, category: tests, who: TA, Shane, priority: high

4) Finish the implementation of id() and key() in patterns.
context: code, packages:org.apache.xalan.xsltc, category: feature, who: ??, priority: high

5) Continue to improve the handling of name spaces. There are a number of bugs that are independent of the lack of namespace nodes. (bugzilla 1411, 1472, 1473, 1506, 1517, 1518)
context: code, packages:org.apache.xalan.xsltc, category: bug, who: ??, priority: high

6) Fix bugs that impact the XSLTMark performance benchmark. (bugzilla 1498, 1532).
context: code, packages:org.apache.xalan.xsltc, category: bug, who: ??, priority: high

7) Fix bugs that impact the use of XSLT with DocBook (1404, 1487).
context: code, packages:org.apache.xalan.xsltc, category: feature, who: ??, priority: high

8) Fix bugs with the handling of variables and parameters (1487, 1408)
context: code, packages:org.apache.xalan.xsltc, category: feature, who: MJ, priority: high

9) Fix bugs reflecting positional problems (1409, 1410, 1412, 1532).
context: code, packages:org.apache.xalan.xsltc, category: feature, who: TM, priority: high

10) Fix bugs on dealing with XPATH expressions (1407, 1511).
context: code, packages:org.apache.xalan.xsltc, category: feature, who: TM, priority: high

11) Fix bugs involving template selection (1503, 1397).
context: code, packages:org.apache.xalan.xsltc, category: feature, who: who, priority: medium

12) Implement name space nodes (bugzilla 1379).
context: code, packages:org.apache.xalan.xsltc, category: feature, who: MJ, priority: low

13) Look into proper caching algorithms and improve the example given in DocumentCache.java accordingly.
context: code, packages:org.apache.xalan.xsltc, category: feature, who: ??, priority: low

14) Implement an extension to support the redirection of output to multiple output files from within a stylesheet (equivalent to xalan:redirect or saxon:output). Note: Task may be implemented as a result of integrating Xsltc and Xalan and using shared code.
context: code, packages:????, category: feature, integration with Xalan, who: ??, priority: medium

15) Implement a node-set extension to convert result tree fragments to node-sets. This enables sorting and grouping of nodes assigned to a tree variable. Note: Task may be implemented as a result of integrating Xsltc and Xalan and using shared code.
context: code, packages:????, category: feature, integration with Xalan, who: ??, priority: medium

16) Add support for nonstatic external Java functions. Note: Task may be implemented as a result of integrating Xsltc and Xalan and using shared code.
context: code, packages:????, category: feature, integration with Xalan, who: ??, priority: medium

17) Fix bugs affecting the correctness of ouput (1403, 1406, 1441, 1489, 1429, 1504, 1508, 1512, 1513, 1516, 1520, 1521, 1525). Note: Task may be implemented as a result of integrating Xsltc and Xalan and using shared code.
context: code, packages:????, category: feature, integration with Xalan, who: ??, priority: medium

18) Use SAX to build the AST. The DOM builder (the real DOM builder, not our quasi-DOM builder) receives SAX events when it builds the DOM. The compiler.Parser class could possible receive these SAX events directly, and thereby eliminating the need for a DOM (saves loads of time and memory).
context: code, AST, category: architecture, who: ??, priority: medium

19) Consider building a DOM-2-'DOM' converter, perhaps by adding a second DOM builder inner class to our DOM. Then we would have one SAX DOM builder and one DOM DOM builder. I don't know if JAXP lets you supply the stylesheet as a DOM. If it doesn't, we should assign this task a very low priority. There is no point in spending a lot of time on this if JAXP users will never be able to use this functionality.
context: code, DOM, category: architecture, who: ??, priority: medium

Completed:

Developers:

A list of some of people currently working on working on XCLTC: