[EMAIL PROTECTED]: Project xml-xalan2-smoketest (in module xml-xalan) failed

ump/public/workspace/xml-xalan/test/java/build/qetest.jar:/usr/local/gump/public/workspace/httpunit/jars/Tidy.jar - smoketest-results-dist: [tar] Building tar: /home/gump/workspaces2/public/workspace/xml-xalan/test/java/build/xalan-smoketest-200

[jira] Commented: (XALANJ-1403) ArrayIndexOutOfBoundsException: -2048 when using IBM JDK1.3.1 and large input xml file

[ http://issues.apache.org/jira/browse/XALANJ-1403?page=comments#action_62015 ] Brian Minchau commented on XALANJ-1403: --- Yash Talwar has just sent me a note indicating that he has seen similar behavior when the transformer object is used a for a

Xalan-J bug triage agenda for Tuesday April 5, 2005

SUBJECT:Xalan-J JIRA defect review WHEN: Tuesday April 5, 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: (???) ???-

[jira] Updated: (XALANJ-1853) package org.w3c.dom.xpath is missing from xalan.jar in 2jars distro

[ http://issues.apache.org/jira/browse/XALANJ-1853?page=history ] Brian Minchau updated XALANJ-1853: -- reviewer: [EMAIL PROTECTED] Filling in the reviewer field. > package org.w3c.dom.xpath is missing from xalan.jar in 2jars distro > ---

[jira] Updated: (XALANJ-1978) Using StreamResult with File argument throws exception

[ http://issues.apache.org/jira/browse/XALANJ-1978?page=history ] Brian Minchau updated XALANJ-1978: -- Xalan info: [PatchAvailable] Checking the "PatchAvailable" box, as there is a suggested fix, by D. Gardner, within this issue. This issue will be dis

[jira] Commented: (XALANJ-1403) ArrayIndexOutOfBoundsException: -2048 when using IBM JDK1.3.1 and large input xml file

[ http://issues.apache.org/jira/browse/XALANJ-1403?page=comments#action_62007 ] Brian Minchau commented on XALANJ-1403: --- Erik, can you give us a testcase please. > ArrayIndexOutOfBoundsException: -2048 when using IBM JDK1.3.1 and large input > x

[jira] Resolved: (XALANJ-1389) apply-templates

[ http://issues.apache.org/jira/browse/XALANJ-1389?page=history ] Brian Minchau resolved XALANJ-1389: --- Assign To: (was: Xalan Developers Mailing List) Resolution: Fixed The reporter of this issue has commented that it is fixed in an earli

[jira] Resolved: (XALANJ-997) java.lang.OutOfMemoryError when processing large CALS tables - memory leak?

[ http://issues.apache.org/jira/browse/XALANJ-997?page=history ] Brian Minchau resolved XALANJ-997: -- Assign To: (was: Xalan Developers Mailing List) Resolution: Cannot Reproduce > java.lang.OutOfMemoryError when processing large CALS table

[jira] Resolved: (XALANJ-1198) Xalan's DOMSource is not thread-safe

[ http://issues.apache.org/jira/browse/XALANJ-1198?page=history ] Brian Minchau resolved XALANJ-1198: --- Assign To: (was: Xalan Developers Mailing List) Resolution: Won't Fix Xalan's DOMSource is not thread safe. But as noted by Joe K. DOMs

[jira] Updated: (XALANJ-1640) xmlns bug using docbook->xhtml xslt on ulink template

[ http://issues.apache.org/jira/browse/XALANJ-1640?page=history ] Brian Minchau updated XALANJ-1640: -- reviewer: [EMAIL PROTECTED] Filling in the reviewer field. > xmlns bug using docbook->xhtml xslt on ulink template > -

[jira] Commented: (XALANJ-997) java.lang.OutOfMemoryError when processing large CALS tables - memory leak?

[ http://issues.apache.org/jira/browse/XALANJ-997?page=comments#action_62001 ] Brian Minchau commented on XALANJ-997: -- Peter, I know that this issue is very old. Joe K. tried to reproduce it with the given information and couldn't. If this is sti

[jira] Resolved: (XALANJ-774) Out of memory running XSL file against large XML, when using SAX

[ http://issues.apache.org/jira/browse/XALANJ-774?page=history ] Brian Minchau resolved XALANJ-774: -- Assign To: (was: Xalan Developers Mailing List) Resolution: Cannot Reproduce Resolving as "Cannot Reproduce" > Out of memory running XSL

[jira] Resolved: (XALANJ-903) infinite loop is generated in xsl:for-each

[ http://issues.apache.org/jira/browse/XALANJ-903?page=history ] Brian Minchau resolved XALANJ-903: -- Assign To: (was: Xalan Developers Mailing List) Resolution: Incomplete > infinite loop is generated in xsl:for-each >

[jira] Updated: (XALANJ-2008) non-private non-final static variables and mutable static variables open potential security holes in Xalan

[ http://issues.apache.org/jira/browse/XALANJ-2008?page=history ] Brian Minchau updated XALANJ-2008: -- reviewer: [EMAIL PROTECTED] Filling in the reviewer field. > non-private non-final static variables and mutable static variables open > potential sec

[jira] Updated: (XALANJ-2054) ExampleContentHandler code looks cut-and-paste typo'ed

[ http://issues.apache.org/jira/browse/XALANJ-2054?page=history ] Brian Minchau updated XALANJ-2054: -- reviewer: [EMAIL PROTECTED] Filling in the reviewer field. > ExampleContentHandler code looks cut-and-paste typo'ed >

[jira] Updated: (XALANJ-1478) bad XSL provides no useful error message

[ http://issues.apache.org/jira/browse/XALANJ-1478?page=history ] Brian Minchau updated XALANJ-1478: -- reviewer: [EMAIL PROTECTED] Filling in the reviewer field. > bad XSL provides no useful error message > > >

[jira] Updated: (XALANJ-1526) getAttributes does not work in ElemExtensionCall subtree

[ http://issues.apache.org/jira/browse/XALANJ-1526?page=history ] Brian Minchau updated XALANJ-1526: -- reviewer: [EMAIL PROTECTED] Filling in the reviewer field. > getAttributes does not work in ElemExtensionCall subtree > --

[jira] Updated: (XALANJ-1824) Current template rule affected by calling named template

[ http://issues.apache.org/jira/browse/XALANJ-1824?page=history ] Brian Minchau updated XALANJ-1824: -- reviewer: [EMAIL PROTECTED] Filling in the reviewer field. > Current template rule affected by calling named template > --

[jira] Updated: (XALANJ-1852) xalan.jar in 2jars distro contains junk manifest entries

[ http://issues.apache.org/jira/browse/XALANJ-1852?page=history ] Brian Minchau updated XALANJ-1852: -- reviewer: [EMAIL PROTECTED] Filling in the reviewer field. > xalan.jar in 2jars distro contains junk manifest entries > --

[jira] Updated: (XALANJ-2085) Need to update Javadoc for org.apache.xpath.domapi package.

[ http://issues.apache.org/jira/browse/XALANJ-2085?page=history ] Brian Minchau updated XALANJ-2085: -- reviewer: [EMAIL PROTECTED] I know this issue has a patch, was revied, was applied to CVS, I'm just marking the reviewer in the review field. > Need

[jira] Updated: (XALANJ-1938) key() and id() results are incorrect, works with Xalan

[ http://issues.apache.org/jira/browse/XALANJ-1938?page=history ] Brian Minchau updated XALANJ-1938: -- Xalan info: (was: [PatchAvailable]) Unchecking the PatchAvaiable, as Henry Z. indicated in the April JIRA triage meeting that he wanted to re-work t

[jira] Commented: (XALANJ-1978) Using StreamResult with File argument throws exception

[ http://issues.apache.org/jira/browse/XALANJ-1978?page=comments#action_61986 ] Gregor J. Rothfuss commented on XALANJ-1978: Will this be tackled any time soon? There are a lot of projects out there, ASF-hosted and otherwise, that rely on X

[jira] Resolved: (XALANJ-2089) Performance degradation in ElemNumber.

[ http://issues.apache.org/jira/browse/XALANJ-2089?page=history ] Yash Talwar resolved XALANJ-2089: - Resolution: Fixed Fix Version: CurrentCVS Patch commited to CVS. > Performance degradation in ElemNumber. > --

[jira] Updated: (XALANJ-2089) Performance degradation in ElemNumber.

[ http://issues.apache.org/jira/browse/XALANJ-2089?page=history ] Brian Minchau updated XALANJ-2089: -- reviewer: [EMAIL PROTECTED] > Performance degradation in ElemNumber. > -- > > Key: XALANJ-2089 >

[jira] Updated: (XALANJ-2090) spec11 testcase added for XML 1.1 support in accept bucket may result in smoketest failure.

[ http://issues.apache.org/jira/browse/XALANJ-2090?page=history ] Brian Minchau updated XALANJ-2090: -- Xalan info: [PatchAvailable] Marking as PatchAvailable. > spec11 testcase added for XML 1.1 support in accept bucket may result in > smoketest failur

[jira] Resolved: (XALANJ-1824) Current template rule affected by calling named template

[ http://issues.apache.org/jira/browse/XALANJ-1824?page=history ] Brian Minchau resolved XALANJ-1824: --- Resolution: Fixed Resloving as "Fixed" because the code was committed to CVS. > Current template rule affected by calling named template >

[jira] Assigned: (XALANJ-1924) Example on http://xml.apache.org/xalan-j/usagepatterns.html uses depricated method

[ http://issues.apache.org/jira/browse/XALANJ-1924?page=history ] Brian Minchau reassigned XALANJ-1924: - Assign To: Brian Minchau > Example on http://xml.apache.org/xalan-j/usagepatterns.html uses depricated > method > --

[jira] Assigned: (XALANJ-2082) Serializer javadoc and comments should be more independent

[ http://issues.apache.org/jira/browse/XALANJ-2082?page=history ] Brian Minchau reassigned XALANJ-2082: - Assign To: Brian Minchau > Serializer javadoc and comments should be more independent > -

[jira] Commented: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

[ http://issues.apache.org/jira/browse/XALANJ-2084?page=comments#action_61968 ] Brian Minchau commented on XALANJ-2084: --- Current behavior is a rather serious exception when the character being written out by the serializer is not a valid charcter

[jira] Commented: (XALANJ-2073) The output format must have a '{http://xml.apache.org/xslt}content-handler' property!

[ http://issues.apache.org/jira/browse/XALANJ-2073?page=comments#action_61970 ] Brian Minchau commented on XALANJ-2073: --- A question for the Xalan team is, what should the serializer do when it can't load these property files, for whatever reason?

[jira] Commented: (XALANJ-2073) The output format must have a '{http://xml.apache.org/xslt}content-handler' property!

[ http://issues.apache.org/jira/browse/XALANJ-2073?page=comments#action_61969 ] Brian Minchau commented on XALANJ-2073: --- Earl, please provide a testcase and more information so that a Xalan developer can reproduce this problem. However, this lo

[jira] Commented: (XALANJ-2089) Performance degradation in ElemNumber.

[ http://issues.apache.org/jira/browse/XALANJ-2089?page=comments#action_61963 ] Brian Minchau commented on XALANJ-2089: --- The attached patch is really the old code back again, but with alphaCountTable cached in an instance variable, rather than a

Reminder of Xalan-J JIRA bug triage - Tuesday April 5

This is a reminder to Xalan-J committers that the monthly JIRA bug triage is coming next week, on Tuesday April 5, 2:00 - 3:30 pm EST. Please book it if you haven't already done so. I'll be sending a detailed agenda with the call in information (same number as before) on Monday to any Xalan-J comm

[jira] Commented: (XALANJ-2087) Get rid of the dependency on sun.io.CharToByteConverter

[ http://issues.apache.org/jira/browse/XALANJ-2087?page=comments#action_61941 ] Brian Minchau commented on XALANJ-2087: --- I added a comment to XALANJ-2086. Yes, sun.io.CharToByteConverter has been effectively out of use since December 2003. We co

[jira] Commented: (XALANJ-2086) Bug in the class org.apache.xml.serializer.Encodings

[ http://issues.apache.org/jira/browse/XALANJ-2086?page=comments#action_61936 ] Brian Minchau commented on XALANJ-2086: --- The dropping of the return value, as noted in this bug report, was introduced a long time ago, December 4, 2003. You're the