Use Advanced Search to search the entire archive.
[jsr363-experts] Re: Early Draft
- From: Werner Keil <
>
- To: "
" <
>
- Subject: [jsr363-experts] Re: Early Draft
- Date: Fri, 19 Dec 2014 13:49:10 +0100
Martin,
Referring to the JCP Process Document:
https://jcp.org/en/procedures/jcp2
*Java Specification (Specification)*: A written specification for some
aspect of the Java technology. This includes the language, virtual machine,
Platform Editions, Profiles, and application programming interfaces.
Although it says "interfaces", the Spec is not the same as the Reference
Implentation, while "soandso-api" is.
A JSR "...produces a Specification, a Reference Implementation (to prove
the Specification can be implemented,) and a Technology Compatibility Kit
(a suite of tests, tools, and documentation that is used to test
implementations for compliance with the Specification.) "
as per JCP document, so the Reference Implementation is not part of the
Spec, while the API is a code manifestation of the Spec.
You argued, types like Measurement or Range should not be in the Spec,
which is why they are "assisting" parts of the RI. Much like
MBeanServerRegistrationUtility in the RI of JSR 107 (it doesn't implement
any of the Spec/API parts, but only helps wiring them with MBeans:
https://github.com/jsr107/RI/blob/master/cache-ri-impl/src/main/java/org/jsr107/ri/management/MBeanServerRegistrationUtility.java
HTH,
Werner