See a list of developers/initials.
Planned releases:
09/??/01 Completed
For release: 09/??/01
, ????
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)
Modify Xalan test enviroment to test XSLTC as a component of XalanJ2.
context: test, packages:org.apache.xalan.xsltc, category: tests, who: TA, Shane, priority: high
2)
Finish the implementation of id() and key() in patterns.
context: code, packages:org.apache.xalan.xsltc, category: feature, who: MJ, priority: high
3)
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, 1506, 1518, 2582, 2801, 2857, 2859, 2863, 2535, 2954, 2840)
context: code, packages:org.apache.xalan.xsltc, category: bug, who: ??, priority: high
4)
Fix bugs that impact the XSLTMark performance benchmark.
(bugzilla 1376, 1498, 1512, 1532, 2351, 2517, 2553, 3065, 3066).
context: code, packages:org.apache.xalan.xsltc, category: bug, who: ??, priority: high
5)
Fix bugs reflecting positional problems (1410, 1532, 2939).
context: code, packages:org.apache.xalan.xsltc, category: bugs, who: TM, priority: high
6)
Fix bugs on dealing with XPATH/Axes expressions (1498, 2551, 2553, 2572, 2932).
context: code, packages:org.apache.xalan.xsltc, category: bug, who: TM, priority: high
7)
Fix bugs involving template selection (1397, 2749, 2582, 2585, 2695, 2749, 2754, 2886, 2937).
context: code, packages:org.apache.xalan.xsltc, category: bug, who: ??, priority: medium
8)
Fix bugs affecting numbering (2901, 2931).
context: code, packages:org.apache.xalan.xsltc, category: bug, who: ??, priority: medium
9)
Fix bugs affecting comment and processing-intruction nodes (2599, 2834, 2858).
context: code, packages:org.apache.xalan.xsltc, category: bug, who: ??, priority: medium
10)
Implement name space nodes (bugzilla 1379).
context: code, packages:org.apache.xalan.xsltc, category: feature, who: MJ, priority: low
11)
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
12)
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
13)
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
14)
Fix bugs affecting the correctness of ouput
(1439, 1504, 1512, 1516, 1520, 1525, 2517, 2520, 2578, 2948, 2951, 2952, 2954, 3005, 3065).
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)
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
16)
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
A list of some of people currently working on working on XSLTC: