JDK-6273765 : ImmutableDescriptor.getFieldValues(non-empty-array) on an empty descriptor returns unexpected array
- Type: Bug
- Component: core-svc
- Sub-Component: javax.management
- Affected Version: 6
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2005-05-20
- Updated: 2017-05-16
- Resolved: 2005-12-21
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 b47Fixed  |
Description
modelmbean.DescriptorSupport behaves as expected but ImmutableDescriptor not despite the method under test is defined in the Descriptor interface they both implement.
The failing test case is based on the javadoc sentence "If the descriptor is empty, you will get an empty array.".
The test does:
Descriptor descr = new ImmutableDescriptor(new String[]{}, new Object[]{});
descr.getFieldValues(new String[]{"missing", "in", "action"}).
I put here the JCK test output :
(TEST) Retrieval with a non empty array on an empty Descriptor
(ERROR) Field values not as expected
GOT = [null, null, null]
EXPECTED = []
###@###.### 2005-05-20 16:31:24 GMT
Comments
|