[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] NEW VOTE 4: Optional Specs for the jakarta namespace
|
+1
LieGrue,
strub
> Am 05.12.2019 um 00:33 schrieb Kevin Sutter <sutter@xxxxxxxxxx>:
>
> Preamble: https://www.eclipse.org/lists/jakartaee-platform-dev/msg01180.html
>
> Please vote +1/0/-1 on the following. Any non +1 vote, please provide reasoning in your reply. Thank you!
>
> Mark Optional (Move to jakarta namespace) - Vote
> • Jakarta Enterprise Web Services 1.4, JSR 109
> • EJB 2.x API Group (Table 18 in EJB 3.2 Spec)
>
> Since the other Web Services related specifications are being proposed as Optional (in Vote 3), we felt it was sufficient to mark JSR 109 as Optional. There is no API associated with this Specification, but there is a TCK and Implementation. So, still some work to do, but we lower the bar for new implementations.
>
> Since there was confusion on the specific EJB APIs that were proposed previously, and there was a mix level of support for pruning, this proposal suggests to mark the EJB 2.x API Group as Optional. Granted, this still leaves work on the table for Jakarta EE 9 (vs pruning), but there seemed to be a greater level of hesitancy on removing this EJB 2.x API Group -- especially since it was never marked optional or deprecated in the past. At least by marking it optional, it lowers the bar for new implementations.
>
> ---------------------------------------------------
> Kevin Sutter
> STSM, MicroProfile and Jakarta EE architect
> e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
> phone: tl-553-3620 (office), 507-253-3620 (office)
> LinkedIn: https://www.linkedin.com/in/kevinwsutter
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
