| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8018703 | 7u45 | Deven You | P5 | Closed | Fixed | b01 |
| JDK-8004161 | 7u40 | Unassigned | P5 | Closed | Fixed | b06 |
New constructor in sun.tools.java.ClassPath builds a path using File.separator instead of File.pathSeparator.Char
When Sun added support for fix 6473331, which adds support for Class-Path manifest entries in JAR files to rmic, they added a new constructor for sun.tools.java.ClassPath:
public ClassPath(String[] patharray)
which calls a new private method:
private void init(String}[] patharray)
The init method builds the String pathstr. The problem is that it separates the path entries by using File.separator instead of File.pathSeparatorChar. Any application that is using the pathstr as a search path will not be able to properly parse the entries. Such an application is the IBM ORB used by Websphere.
Bug Workaround
When Sun added support for fix 6473331, which adds support for Class-Path manifest entries in JAR files to rmic, they added a new constructor for sun.tools.java.ClassPath:
public ClassPath(String[] patharray)
which calls a new private method:
private void init(String}[] patharray)
The init method builds the String pathstr. The problem is that it separates the path entries by using File.separator instead of File.pathSeparatorChar. Any application that is using the pathstr as a search path will not be able to properly parse the entries. Such an application is the IBM ORB used by Websphere.
Bug Workaround
- backported by
-
JDK-8004161 New constructor in sun.tools.java.ClassPath builds a path using File.separator instead of File.pathS
-
- Closed
-
-
-
- Closed
-
- duplicates
-
JDK-6695325 REGRESSION: Classpath returned by sun.rmi.rmic.BatchEnvironment.createClassPath(
-
- Closed
-
- relates to
-
-
- Closed
-