You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Brian Minchau <mi...@ca.ibm.com> on 2005/05/02 20:34:42 UTC
Xalan-J bug triage agenda for Tuesday May 3, 2005
Xalan-J developers,
it is time for the JIRA status meeting, held the first Tuesday of each
month.
If you already got the agenda below with the call in information, then you
need not read further, read the other note.
If you are an active Xalan-J committer who didn't get the call in
information, and would like to attend the JIRA issue triage meeting, please
send me a note and I'll send you the agenda, as below, but with the call in
information.
All active Xalan-J committers are welcome.
Thanks,
Brian Minchau
---------------------------------------------------------------------------
SUBJECT: Xalan-J JIRA defect review
WHEN: Tuesday May 3, 2005 from 2:00 to 3:30 pm EDT
INVITEES: Active Apache Xalan committers
CHAIR: Brian Minchau
WHERE: Teleconference
Phone for Toronto Area: (***) ***-****
Phone for Others: (***) ***-****
Conference ID for all: *******
LAST MEETING WAS ON: Tusday April 5, 2005
Agenda Outline:
1. Old Business
2. Brief Summary of defect arrival and resolution
3. New Issues Opened Since Last Meeting, plus assigned issue status
4. Round table discussion
5. Older open blocker or critical issues
6. Older open non-blocker non-critical issues
AGENDA
======================================================================
1. Old Business
a) In the last meeting this issues were covered: 2092 back through 2068
b) In previous meetings issues covered: 2067 back through 2032
c) status of JDBC code contribution through John G. from someone who has
already signed a ICLA
d) John G.'s progress on understanding use of DTM for issue 1574
======================================================================
2. Brief Summary of defect arrival and resolution
Since the last meeting 22 issues resolved (compared to 27 in March):
2110, 2109, 2105, 2098, 2096, 2095, 2090, 2086, 2082, 2080,
2077, 2075, 2070, 2073, 2066, 2052, 2049, 2046, 2036, 1934,
1924, 1560
Since the last meeting, 19 new issues (compared to 20 in March) :
2111 back through to 2093
So we now have a total of 409 issues not resolved or closed
(compared to 411 on April 5, 2005).
======================================================================
3. New Issues Opened Since Last Meeting, plus assigned issue status
3.a) New issues needing assignment:
???? - since the agenda came out
2111 - NPE in o.a.xml.serializer.ToHTMLStream.endElement()
2108 - incorrect use of xsl:key cause NullPointerException
2107 - java.io.FileNotFoundException error when executing samples with
Tomcat
2106 - EnvironmentCheck fails with java.lang.NoClassDefFoundError
2104 - Improper linefeed after XML declaration for EBCDIC-like encoding
2103 - Case of doctype definiton wrong
2102 - Getting ArrayIndexOutOfBoundException while trasformation with Xalan
shipped with JDK 1.4.2_05
2101 - DTM Usage in a multithreaded environment
2100 - Unrecognised Namespace beginning with '//'
2099 - EXSLT date:day-abbreviation outputs text in user's language instead
of English
2094 - Don't wrap RuntimeExceptions
2093 - Serializer needs an API to set the end of line sequence
3.b) Open assigned issues with no patch (just a reminder):
Brian M. : 2087, 2084, 2050, 1974, 1941, 1698, 1536
Christine L. : 2055, 1447
Henry Z. : 2069, 2057, 1973, 1938, 1851
John G. : 1574
Morris K. : 2076, 2002, 1263, 1139, 1086, 1065, 739
Ramesh M. : 2063, 2062
Santiago P-G : 2040, 2032, 1912, 1485, 1151
Sarah M. : 2065
Yash T. : 2072, 2056, 2043, 2042, 2041, 2039, 2024, 1923, 1403
3.c) Open issues with a patch, needing a reviewer:
2097 - Problem with variable reference followd by self::node() if you use
XSLTC
2023 - NPE in org.apache.xml.serializer.ToHTMLSAXHandler
2001 - normalize-space gives StackOverflowError
1978 - Using StreamResult with File argument throws exception
1867 - XSLTC: xhtml output method is not supported, nor does XHTML doctype
sniffing work
3.d) Open issues with a patch, needing a review by the reviewer (just a
reminder):
Yash T. : 2078
Ilene S. : 2061
Henry Z. : 1978
3.e) Open issues with a patch and review approval, needing a commit to CVS
--- NONE ---
======================================================================
4. Round table discussion
a) possible new 2.7 release now that Xerces is getting close to their
2.7.0 release?
b) impact on Xalan-J of Sun's JAXP 1.3 donation to Apache
.... other discussion
======================================================================
5. Older open blocker or critical issues
1874 - Used memory is not released once OutOfMemoryError occurs
when DTMManager.setIncremental() is set as true.
1873 - StackOverflowError occurs when recursive call of template is
performed many times.
1870 - serialization exception
1863 - XSLT Error (java.lang.ExceptionInInitializerError): null
1862 - XSLTC fails when compiling a stylesheet using java extension
functions
1855 - [XSLTC] NullPointerException using name() with namespace
1845 - Transformation leads to random SAXParseException (data not bounded
properly) when stressed
1797 - generate-id() doesn't work correctly while document hopping
1742 - Order of global variable and param affect the output
1725 - Xalan 2.5.2 XSLTC: <xsl:copy-of> loses both ATTRIBUTES & NAMESPACES
1710 - Incorrect SAXException about bad integral value of a character to be
written out.
1549 - XSLT Error (javax.xml.transform.TransformerConfigurationException):
Could not load the translet class
1402 - Incorrect usage of context ClassLoader for static field
initialization
(The suggested fix was put in XALANJ-1411, the code was applied,
issue resolve - suggest closing this issue)
1324 - XSLTC compiltation error : Branch target offset too large for short
======================================================================
6. Older open non-blocker, non-critical issues (assuming we make it this
far in the agenda)
- - - - - issues from April 5, 2005 meeting that were not assigned - - - -
-
2088 - Passing initial mode from command line
(accepted last meeting as a request, not assigned)
2083 - Data corrupted in Parallel XSL execution
(Got a testcase since last JIRA meeting, not yet assigned)
2071 - DOM2SAX reports Null-Namespace via 'null' value, should be empty
String ""
(Santiago or Ramesh did not accept assignment, still unassigned)
2067 - Multiple executions of transformation having DOM Document as
parameter is not working
(looks like a legitimate bug, no volunteer to assign to)
- - - - - - - - - - - - - - - - - -
2031 - Grouping filter with preceding/following axis produces wrong nodeset
2029 - XML file must contain LF, CRLF or CR are unsupported
2028 - Doc about redirect should be clear about AVTs
2022 - XMLErrorResources and XPATHErrorResources mix messages with Java
code
2020 - XMLErrorResources - some messages not translated
2016 - Text outside elements that can't be represented in specified
encoding is not escaped
2014 - ExsltDatetime functions do not support fractional seconds values
2010 - getMessageAndLocation() api of TransformerException return stack
trace along with the error message 2002 - backward compatibility with
exsl
2001 - normalize-space gives StackOverflowError
2000 - xsl:include with relative href cause MalformedURL on unicode path
1996 - Error needed for xsl:apply-imports evaluated while evaluating
top-level variable
1995 - CachedXPathAPI doesn't cache under some cases
....
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org