[jira] Commented: (XALANJ-2196) Unneeded BCEL classes in Xalan.jar (2 jar version)

[ http://issues.apache.org/jira/browse/XALANJ-2196?page=comments#action_12420766 ] Mark Woon commented on XALANJ-2196: --- Since this appears to be a packaging issue rather than a coding issue, can't 2.7 just be repackaged correctly instead of wating for a

Re: Moving towards common serialization code...

Joseph Kesselman <[EMAIL PROTECTED]> wrote on 07/12/2006 09:08:27 AM: > I haven't reviewed it myself in aeons, so I have no opinion beyond "Yup, > good question." But I definitely approve of shared code, as long as there > aren't irreconcilable conflicts in demands upon it. If both the Xalan and

Fw: Xalan-J JIRA defect review - Tuesday July 11, 2006 from 2:00 to 3:30 pm EDT - Minutes

SUBJECT: Xalan-J JIRA defect review - Minutes WHEN: Tuesday July 11, 2006 from 2:00 to 3:30 pm EDT INVITEES: Active Apache Xalan committers and contributors CHAIR:Brian Minchau WHERE:Teleconference Phone for Toronto Area: (***) ***-

[jira] Assigned: (XALANJ-2260) NPE calling string on nodeset returned from key(qname, nodeset)

[ http://issues.apache.org/jira/browse/XALANJ-2260?page=all ] Henry Zongaro reassigned XALANJ-2260: - Assign To: Henry Zongaro > NPE calling string on nodeset returned from key(qname, nodeset) >

[jira] Assigned: (XALANJ-2261) com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl reset corrupts transformer.

[ http://issues.apache.org/jira/browse/XALANJ-2261?page=all ] Henry Zongaro reassigned XALANJ-2261: - Assign To: (was: Henry Zongaro) > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl reset > corrupts transformer. > --

Re: Moving towards common serialization code...

Hi Neil, I took part in the assessment of the two code bases back in 2004 and fully agree that moving to a shared serializer is the way to go. Thanks for volunteering to work on the DOM L3 migration. +1. Neil Delima/Toronto/[EMAIL PROTECTED] wrote on 07/11/2006 06:37:53 PM: > > Hi All, > >

[jira] Assigned: (XALANJ-2261) com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl reset corrupts transformer.

[ http://issues.apache.org/jira/browse/XALANJ-2261?page=all ] Brian Minchau reassigned XALANJ-2261: - Assign To: Henry Zongaro > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl reset > corrupts transformer. > -

[jira] Commented: (XALANJ-2261) com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl reset corrupts transformer.

[ http://issues.apache.org/jira/browse/XALANJ-2261?page=comments#action_12420684 ] Brian Minchau commented on XALANJ-2261: --- This issue was reviewed at the bug triage on July 11, 2006 > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryIm

[jira] Commented: (XALANJ-2260) NPE calling string on nodeset returned from key(qname, nodeset)

[ http://issues.apache.org/jira/browse/XALANJ-2260?page=comments#action_12420683 ] Brian Minchau commented on XALANJ-2260: --- Henry Zongaro agreed to look at this bug - per the bug triage on July 11, 2006 > NPE calling string on nodeset returned from

[jira] Commented: (XALANJ-2261) com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl reset corrupts transformer.

[ http://issues.apache.org/jira/browse/XALANJ-2261?page=comments#action_12420682 ] Brian Minchau commented on XALANJ-2261: --- Sergei, sorry to take so long to resond. You say that a reset of com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFact

[jira] Commented: (XALANJ-2262) Exceptions from Error Listener Are Ignored

[ http://issues.apache.org/jira/browse/XALANJ-2262?page=comments#action_12420680 ] Brian Minchau commented on XALANJ-2262: --- The code in displayMessage() catches the exception from the user's ErrorListener and ignores it. The right behavior is to thro

[jira] Commented: (XALANJ-2306) Entities are not resolved properly if document instances of a DTD with different internal subsets are loaded recursively

[ http://issues.apache.org/jira/browse/XALANJ-2306?page=comments#action_12420678 ] Brian Minchau commented on XALANJ-2306: --- The test sets the context node to be a node from different input documents, and then references the unparsed-entity-uri fuctio

[jira] Commented: (XALANJ-2305) problem with xsl:copy-of while copying namespace nodes

[ http://issues.apache.org/jira/browse/XALANJ-2305?page=comments#action_12420676 ] Brian Minchau commented on XALANJ-2305: --- Brian Minchau agreed to look at this one, per the bug triage on July 11, 2006 > problem with xsl:copy-of while copying namespa

[jira] Commented: (XALANJ-2301) NPE in ElemTemplateElement for a ElemSort as part of an ElemForEach when dynamically generating a Templates

[ http://issues.apache.org/jira/browse/XALANJ-2301?page=comments#action_12420674 ] Brian Minchau commented on XALANJ-2301: --- Peter has suggested a fix in ElemForEach, however the traceback above shows a problem with ElemApplyTemplates, so it looks lik

[jira] Resolved: (XALANJ-2300) Bug with disable-output-escaping when using XSLTC and 2 TransformerHandler

[ http://issues.apache.org/jira/browse/XALANJ-2300?page=all ] Brian Minchau resolved XALANJ-2300: --- Fix Version: Latest Development Code Resolution: Duplicate Resolving as a duplicate of xalanj-2210 > Bug with disable-output-escaping when usi

[jira] Assigned: (XALANJ-2298) ClassCastException in SymbolTable.addParam() and compilererror

[ http://issues.apache.org/jira/browse/XALANJ-2298?page=all ] Brian Minchau reassigned XALANJ-2298: - Assign To: Henry Zongaro Assigning to Henry per the triage on July 11, 2006. Henry will try to create a smaller testcase. > ClassCastException in S

[jira] Commented: (XALANJ-2298) ClassCastException in SymbolTable.addParam() and compilererror

[ http://issues.apache.org/jira/browse/XALANJ-2298?page=comments#action_12420667 ] Brian Minchau commented on XALANJ-2298: --- Henry Z. suggests that we add DocBook to our regression tests. Maybe in our smoketest? This issue was triaged on July 11, 20

[jira] Commented: (XALANJ-2297) URIResolver passed wrong base URI for nested include/import

[ http://issues.apache.org/jira/browse/XALANJ-2297?page=comments#action_12420662 ] Brian Minchau commented on XALANJ-2297: --- This issue was triaged on July 11, 2006 > URIResolver passed wrong base URI for nested include/import > --

[jira] Commented: (XALANJ-2296) XPath API's does not recognize or find an element added in DOM object runtime.

[ http://issues.apache.org/jira/browse/XALANJ-2296?page=comments#action_12420660 ] Brian Minchau commented on XALANJ-2296: --- Ravi, you should be using the namespace aware methods when manipulating your DOM. Your XPath expression has prefixes and is cle

[jira] Commented: (XALANJ-2293) Error counting nodes when using a variable

[ http://issues.apache.org/jira/browse/XALANJ-2293?page=comments#action_12420653 ] Brian Minchau commented on XALANJ-2293: --- Henry Zongaro also found that when run with xalan interpretive the problem does not exist in the latest development code, but d

[jira] Commented: (XALANJ-2291) XSTLC doesn't handle islands of XML in HTML correctly

[ http://issues.apache.org/jira/browse/XALANJ-2291?page=comments#action_12420650 ] Brian Minchau commented on XALANJ-2291: --- Assigned to Brian M. per the bug triage on July 11, 2006. > XSTLC doesn't handle islands of XML in HTML correctly > --

[jira] Assigned: (XALANJ-2291) XSTLC doesn't handle islands of XML in HTML correctly

[ http://issues.apache.org/jira/browse/XALANJ-2291?page=all ] Brian Minchau reassigned XALANJ-2291: - Assign To: Brian Minchau > XSTLC doesn't handle islands of XML in HTML correctly > - > >

[jira] Resolved: (XALANJ-2290) Received java.lang.ArrayIndexOutOfBoundsException when xsl:varaible storing RTF result

[ http://issues.apache.org/jira/browse/XALANJ-2290?page=all ] Brian Minchau resolved XALANJ-2290: --- Fix Version: Latest Development Code Resolution: Fixed Yash says it is resolved in the latest devopment code. We (the Apache developers) tend

[jira] Resolved: (XALANJ-1753) Received java.lang.ArrayIndexOutOfBoundsException when xsl:varaible storing RTF result

[ http://issues.apache.org/jira/browse/XALANJ-1753?page=all ] Brian Minchau resolved XALANJ-1753: --- Fix Version: Latest Development Code Resolution: Fixed Assign To: (was: Xalan Developers Mailing List) Yash says it is resolved in th

[jira] Commented: (XALANJ-2280) Source Repository link is broken

[ http://issues.apache.org/jira/browse/XALANJ-2280?page=comments#action_12420646 ] Brian Minchau commented on XALANJ-2280: --- This issue was triaged on July 11, 2006. Decision is that a full patch should be created, the web pages rebuilt and re-publish

Re: Moving towards common serialization code...

I haven't reviewed it myself in aeons, so I have no opinion beyond "Yup, good question." But I definitely approve of shared code, as long as there aren't irreconcilable conflicts in demands upon it. If both the Xalan and Xerces teams are convinced of that, I'd say go for it. One architectural ques