The XALAN PMC - Issue Summary I can do a little cleanup for issues (407, 570, 605).
The following summary is on the oldest 33% of unresolved issues. I will continue reviewing the remaining unresolved issues this week and report back to this mail list. Sincerely, Steven J. Hathaway APACHE XALAN/C CurrentSVN Version 1.11 (JIRA ISSUES) -- REVIEW OF UNRESOLVED (July 8, 2011) XALANC-449 // Deny this Patch XALANC-454 // Do Not Commit - Issue is incomplete XALANC-207 // Nothing to Commit XALANC-494 // Nothing to Commit XALANC-517 // Nothing to Commit XALANC-481 // Nothing to Commit, STILL A BUG ? (length is XMLCh count) XALANC-545 // No longer an issue (Resolved) XALANC-549 // Nothing to Commit XALANC-467 // Feature Enhancement - Keep Open (Steven J. Hathaway) XALANC-559 // Nothing to Commit - No patch created XALANC-566 // Nothing to Commit - Architecture reworked XALANC-570 // Trivial bug fix - NEEDS COMMIT after (C++ standards review) XALANC-577 // Declare as Fixed XALANC-531 // Nothing to Commit XALANC-605 // Regression Test Needed (Steven J. Hathaway) XALANC-596 // Nothing to Commit - STILL A BUG ? XALANC-620 // Nothing to Commit - Workaround Only XALANC-612 // Nothing to Commit - FYI: Binary Pkg Developers XALANC-451 // Fixed XALANC-535 // Nothing to Commit - Workaround Only XALANC-639 // Nothing to Commit - FYI: Binary Pkg Developers XALANC-642 // Nothing to Commit - New Documentation =============================================================== XALANC-449 (19-Jan-2005) Dmitry Hayes Specialization of the XalanVector class for POD types. Summary: Deny This Patch Absence of this patch ensures that the current product remains operable. Admin: Mark Thomas, changed the Workflow to "Closed" status (16-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: This has not been committed. It is a structure change to XalanVector that might be dangerous. We need to ensure that the intent of this edit conforms to W3 specs. Absence of this patch ensures that the product remains operable. Before incorporating this patch into the trunk, it needs to be tested in a branch to ensure that it does not break the production libraries. The change is apparently for POD (Plain Old Documentation) output files. It also appears to be non-standard deviation from the W3 specs. The XSLT productions can be accomplished with standard stylesheets and a custom post-processor application. There are insufficient programmers willing to pursue this patch and its issues. It appears to be abandoned by the contributor. Patched Files: xalanc/Include/XalanVector.hpp xalanc/Includ/XalanMemoryManagement.hpp Affected Files: xalanc/PlatformSupport/XalanMemoryManagement.cpp xalanc/PlatformSupport/XalanMemoryManagerDefault.hpp xalanc/PlatformSupport/XalanMemoryManagerDefault.cpp =============================================================== XALANC-454 (25-Jan-2005) Andras Babos Added two command line arguments to handle external schemas (Improvement) Summary: Do Not Commit -- issue incomplete The PATCH file is in reverse DIFF order instead of a proper patch order. There are insufficient committers to evaluate this code change. Admin: Mark Thomas, changed the Workflow to "Closed" status (16-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Validation should still use the XML parser validation in the Xerces-C library, leaving the Xalan executable program unchanged. The patch only supports a single namespace schema file. It probably needs to support more than one namespace schema. The patch supplies the no-namespace schema file. Related: The Xalan -p can be invoked numerous times to add multiple top-level stylesheet parameters. Use this as an example of how to support multiple namespace schema files. =============================================================== XALANC-207 (20-Nov-2002) David Bertoni better cross-platform support by making CRLF optional in output Summary: Nothing to Commit Resolve with no further development required. Current library is working well. Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Different implementations of line endings and ignorable whitespace have caused much concern. This library is not the place to resolve these issues which are better handled with application pre-processor and post-processor support. It is best to adhere, where possible to common standards. FYI: Platforms DOS-WINDOWS (CRLF) UNIX (LF) APPLE-MAC (CR) IBM-APPS (run-length encoding) Transports and Markup SMTP - Email (CRLF) HTTP - WEB (CRLF) XML - Canonical (LF) HTML - ?? (mostly ignored except for preformatted text) Terminals (CR) Line Printers (CRLF) CR = overstrike the previous line LF = advance the paper Old BASIC Programs CR = Statement Continuation Mark LF = End of Statement Mark =============================================================== XALANC-494 (25-Apr-2005) Dmitry Hayes Running conf with different parameters Summary: Nothing to commit Resolve with no further development required. Not a bug. Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. =============================================================== XALANC-517 (14-May-2005) David Hubbard Problem listener not called with stylesheet errors Summary: Nothing to commit Resolve with no further development required. Not a bug. Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: The resolution is either with your application linker or application code. On Linux systems, the application must be linked with enhanced stack framing in order for error and warning messages to be shared between libraries. This is not a problem when using Microsoft. I have experience in this area when creating libraries of custom XPath functions to be registered with the Xalan Transformer libraries at runtime. =============================================================== XALANC-481 (14-May-2005) Dmitry Hayes XalanC doesn't handle correctly the UTF-16 surroate pairs Assigned to: Ashley Zinyk Summary: Nothing to commit, STILL A BUG ? (length is XMLCh count) Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Detail: The string-length() XPath function returns the number of 16-bit XMLCh characters instead of the number of Unicode characters. =============================================================== XALANC-545 (19-Aug-2005) Chris Butt Improper assert statement in FormatterToXML::accumCharUTF Summary: No longer an issue (Resolved) Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Detail: assert(m_stream != 0); is not needed since m_stream is never used. =============================================================== XALANC-549 (20-Aug-2005) Martin Boucher Different query results with XercesParserLiason::createDocument Summary: Nothing to Commit Resolve this issue with no work to be done. Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Detail: Calling the createDocument() method with buildMaps = true forces correct document node order and bypasses some memory management optimizations. =============================================================== XALANC-467 (16-Mar-2005) Erik Rydgren Possibility to install local extension functions in XPathEvaluator Summary: This is a feature enhancement (Keep open) The issue is old. It is incompatible with the current Xerces/Xalan Memory Manager. Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Detail: The issue is old. It is incompatible with the Xerces/Xalan Memory Manager. The patch needs rework to incorporate the Xerces/Xalan Memory Manager. It requires the Function class and its installer/uninstaller to be incorporated into the XPath Evaluator. Comments and examples with XALANC-467 show how this integration can be accomplished. =============================================================== XALANC-559 (12-Sep-2005) David Bertoni ElemAttribute has some broken logic Summary: No patch created Incomplete definition, Resolve with no further work required. Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Detail: No details available. =============================================================== XALANC-566 (06-Oct-2005) Martin Boucher Wrong export/import directive for XalanMemMgrs Summary: Nothing to commit Declare fixed in CurrentSVN. Memory management has been completely reworked between version1.9 and 1.10. Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Detail: The definition of the class XalanMemMgrs did not contains the good export/import directive. XALAN_PLATFORM_EXPORT is used instead of XALAN_DOMSUPPORT_EXPORT. Including <xalanc/DOMSupport/DOMSupportDefinitions.hpp> is required. I discovered this bug while compiling a static library with Visual Studio .Net 7.1. My static library links with the import libs xalan*.lib and xerces*.lib (version nomenclature omitted to not report wrong filenames; using xalan 1.9 and xerces 2.6). Before applying the above solution, I've got warnings LNK4006 from the linker. The compiler's generated operator=() of class XalanMemMgrs was reported as "already defined". When applying the above solution, warnings disappear. =============================================================== XALANC-570 (12-Oct-2005) David Singleton Removal of compiler warnings from STLHelper.hpp Summary: Trivial bug fix - Needs to be Committed Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: This is a trivial bug fix. It should be committed. C++ overloading of operators should have a return. =============================================================== XALANC-577 (22-Oct-2005) Don Hubbard Can access to docs be restricted for xslt document function Summary: Not an issue - nothing to fix Declare as fixed Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Most security access restrictions can be handled using application catalogs and entity resolvers. =============================================================== XALANC-531 (30-Jun-2005) Evgenity Bashevoy Compilation against STLport fails Summary: Nothing to commit: No fix submitted Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: No suggested fixes =============================================================== XALANC-605 (09-Feb-2006) Dmitry Hayes Incorrect output for xsl:number with alphanumeric characters in the format attribute Summary: Regression test needed The Details provided here describe some regression testing that should be done which may uncover more issues. Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: The <xsl:number value="123" format="***"/> currently returns "***123" instead of "***123***" The supplied patch improves on this issue but is probably incomplete. Regression Notes: Strict Interpretation of XSLT-1.0 Sections 7.7 and 7.7.1 Default format = "1." when the format attribute is missing or empty The format token = "1" The separator token = "." The prefix token = empty The end token is the next or last separator token A number list of "1 3 4 88 120" will be formatted as "1.3.4.88.120." Format of "% 01 " The format token = "01" The separator token = " " space The prefix token = "% " The end token is the next or last separator token A number list of "1 3 4 88 120" will be formatted as "% 01 03 04 88 120 " Format of "***" is interpreted a The format token = "1" The separator token = "***" The prefix token = "***" The end token is the next or last separator token A number list of "1 3 4 88 120" will be formatted as "***1***4***5***88***120***" Examples from the XSLT-1.0 Section 7.7.1 Format token "A " generates sequence "A B C ... AA AB AC " Format token "a " generates sequence "a b c ... aa ab ac " Format token "i " generates sequence "i ii iii iv v vi vii viii ix x ... " Format token "I " generates sequence "I II III IV V VI VII VIII IX X ... " Format token "ア " specifies Katakana numbering Format token "イ " specifies Katakana numbering in the "iroha" order Format token "๑ " specifies numbering with Thai digits Format token "א " letter-value="traditional" specifies "traditional" Hebrew numbering Format token "ა " letter-value="traditional" specifies Gregorian numbering Format token "α " letter-value="traditional" specifies "classical" Greek numbering Format token "а " letter-value="traditional" specifies Old Slavic numbering =============================================================== XALANC-596 (27-Jan-2006) Martin Boucher Wrong XPath evaluation with queries starting with ".//" when wrapping a Xerces Document Summary: Bug still present when using XPathEvaluator with xerces wrapper Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: No patch proposed. =============================================================== XALANC-620 (11-May-2006) Spencer E. Chastain Cannot Build with MinGW Summary: Nothing to commit, Workaround Only There is no staff to continue this support. Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Patch submitted to affect a manual work-around solution. This is not to be committed to the trunk. =============================================================== XALANC-612 (06-Mar-2006) Shawn Price XMLMutex fails from XSLT extension Environment: FreeBSD 6.0 (Release) libc++ 5, libpthread.so.2 Summary: Nothing to commit, FYI for binary package developers Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved Details: David Bertoni confirmed that pthread on FreeBSD is a problem with Xerces-C as of 4-Jun-2006 Compile without thread support. =============================================================== XALANC-451 (22-Jan-2005) Tobias Schuette XalanTransformer setStylesheetParam(key, xobject) Summary: Fixed It is possible to pass multiple top-level parameters into XalanTransformer. Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved Details: Top-level parameter passing into XalanTransformer works in the CurrentSVN. I have used this capability with the Xalan command line executable and other XalanTransformer based applications. I use the capability to pass top-level parameters into XalanTransformer when creating the Xalan-C Version 1.11 User Guide web pages. =============================================================== XALANC-535 (19-Jul-2005) Dmitry Hayes If an error/warning message contains not-displayable character for the local encoding, no message is shown at all. Summary: Close, Workaround Documented Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved Details: Proposed patch and comments. =============================================================== XALANC-639 (13-Feb-2007) Dmitry Hayes XalanC doesn't build with AIX v7 and v8 compilers Environment: AIX Summary: No changes submitted, Close Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved Details: The developers of binary distributions should comment if they have ongoing problems. I am adding some updated build information in the Xalan-C/C++ User Guide version 1.11. (Steven J. Hathaway) =============================================================== XALANC-642 (16-Mar-2007) Will Sappington When building for Cygwin, the "install" target creates an invalid path from the prefix (-P | --prefix option) supplied to runConfigure Summary: Declare fixed by documentation Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved Details: The developers of binary distributions should comment if they have ongoing problems. I am adding some updated build information in the Xalan-C/C++ User Guide version 1.11. (Steven J. Hathaway) --------------------------------------------------------------------- To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org For additional commands, e-mail: xalan-dev-h...@xml.apache.org
