Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE

[Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>]

Hi,

   shouldn't one of the proposed lists also contain "Jakarta Web 
Services Metadata" spec which, as of Java EE 8/Jakarta EE 8, is 
explicitly defined by the EE platform spec to be provided (current specs 
do not say this particular API can be taken from SE)? This metadata spec 
also has not been part of initial Jakarta EE 8 release (likely because 
SE 8 contains same version).
   SAAJ/JAXWS are currently defined to be provided by the Java SE 
platform, from which both were removed in version 11. Is the vote for 
adding/pruning of these two specs in Jakarta EE platform going to run 
together with vote for minimal required Java SE version(s) or after it?

thanks,
--lukas


On 11/17/19 5:56 PM, Steve Millidge (Payara) wrote:
> See previous email for context.
>
> All committers please vote on this proposal for specifications to be 
> pruned from the Jakarta EE 9 platform specifications.
>
> The following specifications will be *removed* from Jakarta EE 9 Full 
> profile specification.
>
> - Jakarta XML Registries JSR 93
>
> - Jakarta XML RPC  JSR 101
>
> - Jakarta Deployment JSR 88
>
> - Jakarta Management JSR 77 note this was not optional or deprecated in 
> Java EE 8
>
> - Jakarta Enterprise Bean entity beans – Note this is old style CMP and 
> BMP entity beans NOT JPA Entities
>
> - Jakarta Enterprise Bean interoperability
>
> - Jakarta Enterprise Bean 2.x and 1.x client view
>
> - Jakarta Enterprise Web Services  JSR 109
>
> Please vote by reply with +1, 0, -1 in accordance with the Eclipse 
> Development Process.
>
> Thanks
>
>
> Steve
>
>
> _______________________________________________
> 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