Hi,
On Tue, Dec 29, 2015 at 12:04 PM, Werner Keil <werner.keil_at_gmail.com> wrote:
> That's certainly something to look at once the standard is established,
> but not at this stage, otherwise it may never get there;-)
>
Especially that last point is an item I'm concerned about.
This is my first time on an EG (together with JSF), and beforehand I knew
that progress in an EG is generally somewhat slower than say an open source
project. Still, when we started I hadn't really imagined that by the end of
this year we missed the EDR, didn't had an actual RI project yet and
subsequently no actual binary release.
Now other EGs have been slow too, like the somewhat related JSR 351, but
for a JSR that's part of the Java EE release train I can't escape the
feeling that progress for the EE 7 and especially EE 6 JSRs (on which I
approximately based the JSR 375 timeline before joining) was somewhat
bigger.
So I really hope that we can get these deliverables released in early 2016.
> Looking e.g. at JSRs like 354, once it was out, integration with other
> JSRs by the community started, e.g. Zalando now has both JSON support (with
> Jackson, the JSON-B JSR is also still in the EE 8 pipeline) or Bean
> Validation.
>
Interesting to hear about Zalando. They were an important customer of us
when it worked at Zanox ;)
Kind regards,
Arjan Tijms