Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] [External] : Re: Proposal for handling "optional" features in Jakarta EE Working Group's specification

Kevin,

This is the total of the notes from the May 5th discussion (which I was unable to attend due to the hour of the meeting):

  • Proposal for how to handle optional features in Jakarta EE specifications including Platform and Web Profile. The proposal is here.

Committee to continue to review, provide comments on the mailing list and in the document. To be explored further in the next meeting.

I'm a bit unclear if this proposal is just addressing the Platform and Platform Profile specifications. This might be more clearly stated (if this is correct or not) at the outset of the proposal.

I'd recommend reviewing the following sections of the Platform 9 Specification to determine if these sections cover, or can be worked to cover, the proposal:

Currently, profiles may declare features and/or component APIs as optional as well. We may want to disallow that both in the Platform and also for Profiles.

While we are interested in lessening the burden of ratification, we may also want to solicit input from users to see if there is still perceived benefit to features that we might want to formally remove. For example, I am pretty sure that Oracle users continue to use elements of Jakarta XML Web Services and also SOAP with Attachments, even though these are relatively stable APIs. I am aware that products may continue to include these but there's still a potential for perception concerns.

Hope this is useful,

-- Ed



On 5/5/2021 6:52 AM, Kevin Sutter wrote:
Just to show that I found this thread...  ;-)  

We started this discussion on today's Spec Committee call.  Limited participation, but the general direction seemed to be acceptable.  A couple of participants would like more time to digest the document before commenting.  Please review the meeting minutes for our discussion points.  

Let's use this thread to discuss any additional items before our next Spec Committee call.

---------------------------------------------------
Kevin Sutter
STSM, Jakarta EE and MicroProfile architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter

Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)



From:        Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx>
To:        Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:        04/30/2021 14:18
Subject:        [EXTERNAL] [jakarta.ee-spec.committee] Proposal for handling "optional" features in Jakarta EE Working Group's specification
Sent by:        "jakarta.ee-spec.committee" <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx>




Dan Bandera in collaboration with Scott Stark and Kevin Sutter authored a proposal for how the Jakarta EE Working Group should handle "optional" features in specifications. The document is here, please review, provide comments and suggested edits. I will include this as an agenda topic in our Specification Committee call on Wednesday, May 5th.

Thanks ... Paul

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee




_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee__;!!GqivPVa7Brio!N_WoPCaCrfEcEG73SHKUSqww_iSFkGYyWJjIh2ZI3oy_BkfYskQjm3KePakvN7w$

Back to the top