For XalanC PMC -- for comment and review Here is another review of outstanding JIRA XALANC issues. Combine this with my report of July 8, 2011.
Sincerely, Steven J. Hathaway ====================================================================== APACHE XALAN/C CurrentSVN Version 1.11 (JIRA ISSUES) -- REVIEW OF UNRESOLVED (July 14, 2011) ADD TO REPORT -- REVIEW OF UNRESOLVED (July 8, 2011) XALANC-535 // Deny this patch XALANC-643 // Deny this patch - new documentation (Steven J. Hathaway) XALANC-644 // Being resolved - new documentation (Steven J. Hathaway) XALANC-649 // Nothing to Commit - new documentation (Steven J. Hathaway) XALANC-663 // Nothing to Commit - future enhancement (XHTML) XALANC-665 // Nothing to Commit - Keep Open XALANC-670 // Nothing to Commit - issue not verified XALANC-666 // Fixed XALANC-676 // Keep Open - needs review XALANC-682 // Fixed XALANC-687 // Trivial bug fix - (GCC 4.3 compiler warning issue) XALANC-688 // Incomplete Patch XALANC-691 // Review for Commit XALANC-695 // Documentation - Sun Studio versions XALANC-693 // Documentation - OpenSolaris XALANC-692 // Fixed XALANC-696 // Being resolved - new documentation (Steven J. Hathaway) XALANC-697 // Nothing to Commit - new documentation (Steven J. Hathaway) XALANC-701 // Review - submission not in unified diff - patch - format =============================================================== XALANC-535 (19-Jul-2005) Dmitry Hayes If an error/warning message contains not-displayable character for the local encodiing no message is shown at all Summary: Deny this patch! (additional comments requested) Admin: Mark Thomas, changed the Workflow to "Closed" status (16-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Patch files have been submitted - not committed. UTF-8 encoding will not work with EBCDIC and some other local encodings. =============================================================== XALANC-643 (18-May-2007) Petteri Raty xalanc fails to compile with -Wl,--as-needed Summary: Keep Open - Library Build Info - DO NOT COMMIT Admin: Mark Thomas, changed the Workflow to "Closed" status (16-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Submitting this patch may break the other Unix builds. =============================================================== XALANC-644 (18-May-2007 ) Petteri Raty Links to bugs in xalanc web pages are wrong Summary: Being fixed in documentation (Steven J. Hathaway) Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: The Web Pages are being rewritten for Xalan-C/C++ Version 1.11. The many broken linkages are being repaired. This one will link to a filtered set of open JIRA issues. I am building new web pages for Xalan-C/C++ Version 1.11. The following link retrieves the outstanding JIRA issues https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+XALANC+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC =============================================================== XALANC-649 (13-Jun-2007) Ovanes Markarian Wrong include paths in the online documentation Summary: No fix submitted - See XALANC-713 for review Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Verify with XALANC-713 (See new doxygen configuration file) - Resubmit if required. I have built a new doxygen configuration file to create Xalan-C/C++ API Reference. for version Xalan-C/C++ version 1.11 The file should also work with the Version 1.10 documentation distribution on Unix systems. (Steven J. Hathaway) =============================================================== XALANC-663 (27-Oct-2007) Denis Gourlaouen Support for XHTML Output Method Summary: Not for XSLT 1.0 - Future Enhancement (Needs reviewer comments) Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: So, I've created a patch that adds a basic XHTML output method to XalanC (according to http://www.w3.org/TR/xslt-xquery-serialization/#xhtml-output) : - handling of EMPTY html elements - addition of a space before the trailing /> - xmlns attributes are output only on the root element (html) provided that the tags in the XSLT file are in the correct namespace - no ''' are generated (as this was also the case with FormatterXML) XHTML can usually be serialized using the XML output method. =============================================================== XALANC-665 (27-Nov-2007) Dmitry Gorbenko Russian language in attribute variables become coded into HTML escape sequence Environment: GNU/Linux, x86_64, CentOS 4.3 ./Xalan --version Xalan version 1.10.0 Xerces version 2.7.0 Summary: No patch available Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: David Bertoni commented: It looks like we specifically used numeric character references in attribute values for compatibility purposes. I tried Saxon, and it's doing the same thing. However, Xalan-J no longer uses numeric character references -- it just uses the actual characters. The character refererences are required only if the output encoding does not support the characters and the characters do not conflict with serialization markup rules. =============================================================== XALANC-670 10-Apr-2008 David Bertoni FormatterTreeWalker needs to filter out XML namespace prefix binding from the document element Summary: No patch available - not confirmed Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: We should never serialize the namespace binding that is automatically added to the document element of every instance of the data model. FormatterTreeWalker needs to be updated to do this. =============================================================== XALANC-666 (15-Jan-2008) Lubomir Kundrak [PATCH] Fedora patches for xalan-c Summary: Fixed : ASF #649853, ASF #651672 Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Patches for Fedora build of Xalan-C Committed by David Bertoni #649853 19-Apr-2008 #651672 25-Apr-2008 =============================================================== XALANC-676 (06-Jun-2008) Aleksandr Vinokurov XalanTransformer's EntityResolver fails to work on Posix platforms in case of entity file absence Environment: Solaris 5.9, Solaris 5.10 Summary: Suggested Patch - Needs Review Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Ref: Xerces-C Bug: JIRA XERCESC-1807 Need to review the "xalan-676.patch" file. Files Affected: XSLT/XSLTProcessorEnvSupportDefault.cpp Note: There are two separate methods for resolving entities. This patch only affects one. We may also need to support custom resolvers based on the OASIS Catalog specification. Other than custom resolvers which are application dependent, we only support a default resolver as a convenience for our users. I don't have time to resolve this issue until October 2011. (Steven J. Hathaway) =============================================================== XALANC-682 (10-Sep-2008) David Bertoni Xalan-C does not implement XSLT erratum 23 for xsl:number Summary: Fixed - Close Issue Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: For xsl:number, with level="any", if there are no matching nodes, Xalan-J generates a text node with "0". The erratum states that, if there are no matching nodes, there will be no text node in the result tree. This issue is related to XALANJ-2458 XALANC-682.patch file submitted Patch Committed 17-Sep-2008 =============================================================== XALANC-687 (02-Feb-2009) John Keeping Remove compiler warning from XalanVector.hpp with GCC 4.3 Summary: Trival Patch - GCC 4.3 Compiler Warnings Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Files Affected: Include/XalanVector.hpp Insert Parentheses in code ensuring operator precedence instead of implied precedence. There is no change in functionality. =============================================================== XALANC-688 (26-Mar-2009) Chris Ostler Allow building as static library Environment: Windows Summary: Incomplete Patch Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: The supplied patch is incomplete. The windows *.vcproj files need updating. The patch only edits the following files: Include/VCPPDefinitions.hpp XPathCAPI/XPathCAPI.h (-- possibly an incomplete edit --) The windows projects for each version of MS Visual Studio may need updating. Therefore the implementation of this patch is incomplete. (Steven J. Hathaway) =============================================================== XALANC-691 (16-Jun-2009) Moddi Te'eni Xstring is created with already cached number Summary: Patch Available - Review for commit Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Patch Available: XALANC-691.patch I am unsure whether this patch has been committed to the SVN repository. =============================================================== XALANC-695 (18-Jun-2009) Meena New compilers do not take -xarch=v9 should use -m64 instead Environment: OpenSolaris Sun studio12 compiler Summary: Partial Patch, Documentation Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: This is an edit to the xalan/c/<trunk>/runConfigure script. I have some documentation so that users building from sources can resolve the issue. This documentation is in the new Xalan-C/C++ User Guide web pages. (Steven J. Hathaway) I am unsure on how many old Sun compilers exist. I am also unsure on how architecture dependency information is to be tested with GNU autoconfig utilities. Integrating the solution into the autoconfig platform should be the preferred situation. (Steven J. Hathaway) Some clarification on Sun compiler release history would be appreciated. (Steven J. Hathaway) =============================================================== XALANC-693 (18-Jun-2009) Meena Makefile.incl.in should look for 64 bit libraries in $XERCESROOT/lib/64 automatically AND should not hardcode xerces-c library version (2.7 in this case) Environment: OpenSolaris Summary: Architecture specific information Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: The patch is rendered in the details instead of an attached file. It needs someone with OpenSolaris experience and general Unix experience to resolve this issue. The platform tools are also required. I don't like to make changes that affect multiple platforms when such dependencies are addressed. Fixes to one environment may break other environments. =============================================================== XALANC-692 (18-Jun-2009) Meena stricmp is missing in some operating systems Environment: OpenSolaris x86 Summary: Needs Resolution (Fixed) Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Fixed with small patch and documentation, supporting all Unix environments. =============================================================== XALANC-696 (10-Feb-2010) Martin von Gagern Parallel build fails Environment: Gentoo Linux, GNU Make 3.81 Summary: Serial build does not fail. Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: Parallel builds require an enhanced dependency specification. The libraries build OK as serial build. In xalanc/Makefile.in, the "lib" target depends on "locale" and "compile", among others. "compile" in turn depends on $(ALL_OBJECTS). Some objects in $(ALL_OBJECTS) do in fact require the LocalMsgIndex.hpp installed by the locale target. This dependency isn't expressed in the Makefile, though. In a serial build, "locale" will be built before "compile", and all is well. In a parallel build, however, i.e. passing "-j5" or similar to make, it is legal for make to build "locale" and "$(ALL_OBJECTS)" at the same time, causing the build to fail with an error message like this: In file included from .../xalanc/PlatformSupport/ExecutionContext.hpp:32, from .../xalanc/PlatformSupport/ExecutionContext.cpp:19: .../xalanc/PlatformSupport/ProblemListenerBase.hpp:28:29: error: LocalMsgIndex.hpp: No such file or directory =============================================================== XALANC-697 (12-Apr-2010) Ivan Leaks with XalanTransformer and external functions Environment: Win32 MSVC6 Summary: See detail documentation Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: See XalanTransformer::uninstallExternalFunction cleans up first and second of the m_functionPairs element, while XalanTransformer's destructor only cleans up second. If you don't uninstallExternalFunction and delete the transformer you have a leak. Also, the Apache samples on extension functions http://xml.apache.org/xalan-c/extensions.html present a Function::clone without parameters that does not exist; and if you happen to new ignoring the memory manager then the memory is not claimed by xalan (use the puzzling XalanCopyConstruct and Xalan does claim it). =============================================================== XALANC-701 (28-Jul-2010) Michael Kupchuk Fix on bad XALAN-675 fix Summary: Committed? - Needs review Admin: Mark Thomas, changed the Workflow to "Closed" status (17-Feb-2011). Jira: Stills shows: Open, Unresolved. Details: The patch files are not in unified diff patch format. There is no comment indicating that the patch has been applied to the SVN repository. =============================================================== --------------------------------------------------------------------- To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org For additional commands, e-mail: xalan-dev-h...@xml.apache.org
