[JSR-354] Strawman scope - JavaSE only
- From: Stephen Colebourne <scolebourne@...>
- To: jcurrency_mail@...
- Subject: [JSR-354] Strawman scope - JavaSE only
- Date: Thu, 7 Feb 2013 17:55:25 +0000
This is a strawman for an JavaSE only JSR.
- the JSR goal would be to add code to OpenJDK in JDK 1.9
- none of the JSR code would be usable before JDK 1.9 is released
- the scope of the JSR would be targetted explicitly at what is
appropriate for JavaSE
- that scope is likely to be primarily about e-commerce and financial
accounting, rather than high-frequency trading or high-end finance
- package name either java.money or javax.money (see below)
- example scope
-- final value type class - Money
-- enhancements to existing Currency class
-- interface CurrenyUnit
-- interface MonetaryAmount
-- mechanism to perform pluggable calculations, such as MonetaryAdjuster
- no separate TCK, as integrated into OpenJDK/JDK .9
- no separate specification, just Javadoc on code proposed to OpenJDK
- code can rely on language and library features of JDK 1.8
This outline is achievable and small in scope (much smaller than JSR-310).
This strawman is strict wrt OpenJDK inclusion being the primary goal.
Full integration into JDK 1.9 and OpenJDK must be achieved before
considering java or javax package name. If the group, having completed
the primary task of code ready for JDK 1.9, wished to continue to
write a spec usable on JDK 1.7 or1.8, then it could. The steps would
- request the javax.money package
- write a standalone TCK
- write a standalone specification
- define other items/features that exist beyond the base spec
It is vitally important not to lock down any specification that is
intended to be part of JDK 1.9 until it is integrated into OpenJDK and
Oracle are happy with it.