[JSR-354] Public Review will be late - latest updates
- From: Anatole Tresch <atsticks@...>
- To: Jsr 354 JavaMoney Public Mailinglist <jcurrency_mail@...>
- Cc: Mark Davis <mark@...>, David Beaumont <dbeaumont@...>, "Cech Previtali Susanne (KIVO)" <susanne.cechprevitali@...>, "Baldry Scot (CS)" <scot.baldry@...>, Harold Ogle <harold.ogle@...>
- Subject: [JSR-354] Public Review will be late - latest updates
- Date: Wed, 25 Sep 2013 02:47:08 +0200
I just wanted to inform you, that the anticipated Public Review will be
postponed. Reason behind is that I, Stephen Colebourne and Werner Keil had
a couple of intense but very good discussions, which will have a direct
effect on our JSR. The outcome if it will be a great improvement and
simplicity of all code APIs and most of all, they lead to a possible great
reduction of the JSRs footprint overall.
I will drop another more detailed, when the code will be update, hopefully
tonight Pacific time. As first hint I would like to summarize our thinkings
- the core API cam be reduced to CurrencyUnit, MonetaryAmount,
MonetaryAdjuster, MonetaryQuery and MonetaryException
- the reference implementation will contain: Money, RoundedMoney,
MoneyCurrency, MonetaryFunctions, MonetaryRoundings, MoneyCurrencyProvider
and possible a simple MonetaryAmountFormatter
The overall design was discussed and will be fully 310 styled, which makes
completely sense (see the details later).
Basically all other functionality defined so far, can
- The currernt format package will be moved to the extras part
- The current exchange package will be moved to the extras part.
- The current extensions part will be moved to the extras part.
So basically, only the minimized core part will be left over as part of the
JSR. The reasons behind are
- After Public Review, we must deliver a full reference implementation
and a TCK. The current resources on the JDK will not allow to deliver all
parts as discussed so far in a reasonable time.
- The basic core infrastructure clearly shows, that it is possible, to
implement such things on top of it. So the API supports all this things,
nevertheless it is questionable, if our JSR also should standardize them,
within this first release-
- Finally all artifacts written so far, are not lost. We plan to move
them over into their own OSS project, where they can be used and further
developed, by whoever may profit of them.
- Additionally, when also Jodamoney would support this JSR, these
extensions done would, completely interoperable with Jodamoney and also
other implementations, since they share the same common mechanisms.
- Basically for a version 1.0 JSR is is a reasonable scope, we can still
do a maintenance release later, if there is reason to add more
So basically, beside that neither the code base nor the spec currently
reflects these aspects, everybody is invited to leave his comments... ;-)
Java Lead Engineer, JSR Spec Lead
CH - 8620 Wetzikon
*Switzerland, Europe Zurich, GMT+1*
Mobile +41-76 344 62 79*