Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
2.7.1
-
None
-
None
-
Operating System: All
Platform: All
-
10519
Description
This problem was reported by Christina Lau's team. If WSAD is started from a
path like c:\wsappdev.exe, we will see a StringIndexOutOfBoundsException from
the SystemIDResolver class when doing a transform for any XSL that imports
another XSL.
In this case, ProcessorInclude.parse() gets a DOMSource object from an external
URIResolver. The SystemId of this DOMSource object is null. Then the TreeWalker
class will set the SourceLocator's SystemId to the "user.dir" system property,
which happens to be "c:\" in this case. SystemIDResolver.getAbsoluteURI() will
throw the described exception because it expects somthing after the "\" char.