[jira] [Commented] (XALANJ-2639) xalan-j class org.apache.xml.utils.SystemIDResolver implementation
"Mukul Gandhi (Jira)" <[email protected]> Sat, 9 May 2026 11:11:00 +0000 (UTC)
| Newsgroups | gmane.text.xml.xalan.devel |
|---|---|
| Message-ID | <[email protected]> |
[ https://issues.apache.org/jira/browse/XALANJ-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18079668#comment-18079668 ]
Mukul Gandhi commented on XALANJ-2639:
--------------------------------------
[~elharo] Within the package org.apache.xml.utils, there are few classes like StylesheetPIHandler, XMLString, FastStringBuffer that're core to Xalan implementation and are written by early Xalan implementation team. I think, moving the package org.apache.xml.utils to xerces or xml-commons may create confusion. May be, we can rename the Xalan package org.apache.xml.utils to org.apache.xsl.utils if that may help. Also, there's a Xalan package org.apache.xml.utils.res that further should make us cautious to do any refactoring to packages org.apache.xml.utils & org.apache.xml.utils.res.
> xalan-j class org.apache.xml.utils.SystemIDResolver implementation
> ------------------------------------------------------------------
>
> Key: XALANJ-2639
> URL: https://issues.apache.org/jira/browse/XALANJ-2639
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in Xalan projects. Anybody can view the issue.)
> Components: TestHarness-TestCase
> Affects Versions: The Latest Development Code
> Reporter: Mukul Gandhi
> Assignee: Mukul Gandhi
> Priority: Major
> Fix For: xslt3.0_alpha1
>
>
> Currently, the XalanJ test SystemIDResolverAPITest fails on Linux (but passes on Windows). This test class, tests the implementation of XalanJ functionality within class SystemIDResolver. The methods like SystemIDResolver.getAbsoluteURIFromRelative(..) within XalanJ codebase may probably have bug, since their results are not consistent between Windows and Linux.
> Joseph Kessselman has helped us, identify this bug.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)