On Tue, Dec 29, 2015 at 4:17 PM, arjan tijms <arjan.tijms_at_gmail.com> wrote:
> 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.
>
So do I and I assume others. Especially JSR 354 which saw a Spec Lead
change (as did e.g. the now rejected JSR 350, an example that no Spec Lead,
not even Oracle in its case is immune to that or "more equal" at least not
for JSRs, I would not say quite the same for many areas of OpenJDK right
now;-)
We have a fairly transparent and democratic setup, not so different from
e.g. how JSR 354 created most artifacts. The spec document there is also
Asciidoc, which means, in theory every EG member has the right and ability
to contribute (and at least some probably should do soon;-)
Judging from other (Oracle lead) EE JSRs I cannot say, if the TCK will be
fully open here, though I would very much hope so. Everything else, looking
at JSRs mostly under the "Glassfish" umbrella is very open and transparent.
And if you look at JSF (I'm not in the current EG but was for 1 or 2 before
it) there are also multiple active contributors other than Oracle and Ed.
>
>
>
>> 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 ;)
>
Where it helps them to identify and suit their customers better, I'd
imagine, they may some day also use some of what's created here;-D
>
> Kind regards,
> Arjan Tijms
>
>
Kind Regards,
Werner