JDK-5096178 : rmic should not generate code that constructs new instances of java.lang.Boolean
- Type: Enhancement
- Component: core-libs
- Sub-Component: java.rmi
- Affected Version: 1.4.2
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2004-09-02
- Updated: 2005-09-20
- Resolved: 2005-09-20
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6 betaFixed  |
Related Reports
|
Relates :
|
Description
The current rmic implementation generates code that always constructs a new instance of java.lang.Boolean to box a boolean value (to pass to RemoteRef.invoke). The generated code would be more efficient (in space and time) if instead of this: new Boolean(x) it did this: (x ? Boolean.TRUE : Boolean.FALSE) [In the J2SE 1.4 API, java.lang.Boolean provides a static factory method, "valueOf", for this purpose, but rmic cannot in general generate stub classes that assume a 1.4 platform.]
Comments
|