Re: [ejb-dev] Request for review on PR# 74 and 75

[<Hussain.NM@xxxxxxxxxxxxx>]

Yes, Kevin you are right about the PR not being focused on converting Java EE to Jakarta EE.

What I have in mind is to do the following:

• Pass 1: Format the specification document AS-IS to match the Java EE version 8. (2 weeks)
• Pass 2: Change references from Java EE to Jakarta EE and publish it as Jakarta Enterprise Beans 3.2 (replace the current straw man) (1 week)
• Pass 3: Make updates to package name, schema, removals etc. and get it ready for Jakarta Enterprise Beans 4.0 (2 weeks)

Thanks

Hussain

---

From: Kevin Sutter <sutter@xxxxxxxxxx>
Sent: Wednesday, March 4, 2020 10:21 PM
To: ejb developer discussions <ejb-dev@xxxxxxxxxxx>
Cc: N M, Hussain (Cognizant) <Hussain.NM@xxxxxxxxxxxxx>
Subject: RE: [ejb-dev] Request for review on PR# 74 and 75

 

Thanks for the review, Bill!  I agree with your comment about JSR 109 being in Jakarta EE 8.

My one comment is whether you were looking to do the Jakarta EE 9 changes with this commit or not.  Some of my earlier comments on the other PRs were not accepted (yet) since you were just focused on getting to the Jakarta EE 8 equivalent.  If that's still the case, then increasing all of the Spec version levels is pre-mature.  But, since the end goal is to get this Spec ready for Jakarta EE 9, then let's do all of the required changes now. Thanks!

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



From:        Bill Shannon <bill.shannon@xxxxxxxxxx>
To:        ejb developer discussions <ejb-dev@xxxxxxxxxxx>, Hussain.NM@xxxxxxxxxxxxx
Date:        03/04/2020 10:40
Subject:        [EXTERNAL] Re: [ejb-dev] Request for review on PR# 74 and 75
Sent by:        ejb-dev-bounces@xxxxxxxxxxx

---

I just scanned the table but it looked right to me.

However, JSR 109 is in Jakarta EE 9.  It's Jakarta Enterprise Web Services 1.4.

Hussain.NM@xxxxxxxxxxxxxwrote on 3/3/20 9:53 PM:

Regarding the changes requested in PR #75, I would like to know if the below table depicts the expected changes:

Existing	New
[[[a9850, 1]]] Enterprise JavaBeans™, version 3.2. (this specification)  http://jcp.org/en/jsr/detail?id=345.	[[[a9850, 1]]] Jakarta Enterprise Beans (Core) 4.0. (this specification)  https://jakarta.ee/specifications/enterprise-beans/4.0/.
[[[a9851, 2]]] Java™ Persistence API, version 2.1.  http://jcp.org/en/jsr/detail?id=338	[[[a9851, 2]]] Jakarta Persistence 3.0.  https://jakarta.ee/specifications/persistence/3.0/
[[[a9857, 8]]] Java™ Transaction API, version 1.2 (JTA).  http://jcp.org/en/jsr/detail?id=907.	[[[a9857, 8]]] Jakarta Transactions 2.0.  https://jakarta.ee/specifications/transactions/2.0/.
[[[a9861, 12]]] Java™ Platform, Enterprise Edition Specification Version 7 (Java EE). http://jcp.org/en/jsr/detail?id=342	[[[a9861, 12]]] Jakarta EE Platform 9.  https://jakarta.ee/specifications/platform/9/.
[[[a9862, 13]]] Java™ Message Service, version 2.0 (JMS).  http://jcp.org/en/jsr/detail?id=343.	[[[a9862, 13]]] Jakarta Messaging 3.0.  https://jakarta.ee/specifications/messaging/3.0/.
[[[a9863, 14]]] Java EE™ Connector Architecture, version 1.7 (Connector).  http://jcp.org/en/jsr/detail?id=322 .	[[[a9863, 14]]] Jakarta Connectors 2.0.  https://jakarta.ee/specifications/connectors/2.0/ .
[[[a9873, 24]]] Java™ API for XML-based RPC, version 1.1 (JAX-RPC).  http://jcp.org/en/jsr/detail?id=101.	[[[a9873, 24]]] Jakarta XML RPC 1.1.  https://jakarta.ee/specifications/xml-rpc/1.1/.
[[[a9878, 29]]] Web Services Metadata for the Java Platform, version 2.1.  http://jcp.org/en/jsr/detail?id=181.	[[[a9878, 29]]] Jakarta Web Services Metadata 3.0.  https://jakarta.ee/specifications/web-services-metadata/3.0/.
[[[a9881, 31]]] Java™ API for XML-based Web Service, version 2.2 (JAX-WS). http://jcp.org/en/jsr/detail?id=224.	[[[a9881, 31]]] Jakarta XML Web Services 3.0.  https://jakarta.ee/specifications/xml-web-services/3.0/
[[[a9886, 36]]] Managed Beans, version 1.0 (Managed Beans).  http://jcp.org/en/jsr/detail?id=316.	[[[a9886, 36]]] Jakarta Managed Beans 2.0.  https://jakarta.ee/specifications/managedbeans/2.0/.
[[[a9887, 37]]] Interceptors, version 1.2.  http://jcp.org/en/jsr/detail?id=318.	[[[a9887, 37]]] Jakarta Interceptors 2.0.  https://jakarta.ee/specifications/interceptors/2.0/.
[[[a9888, 38]]] Contexts and Dependency Injection for the Java EE Platform 1.1 (CDI specification)  http://jcp.org/en/jsr/detail?id=346.	[[[a9888, 38]]] Jakarta Context Dependency Injection 3.0  https://jakarta.ee/specifications/cdi/3.0/.
[[[a9889, 39]]] The Java API for RESTful Web Services, version 2.0 (JAX-RS)  http://jcp.org/en/jsr/detail?id=339.	[[[a9889, 39]]] Jakarta RESTful Web Services 3.0  https://jakarta.ee/specifications/restful-ws/3.0/.
[[[a9890, 40]]] EJB 3.2 Optional Features  http://jcp.org/en/jsr/detail?id=345	[[[a9890, 40]]] Jakarta Enterprise Beans (Optional) 4.0.  https://jakarta.ee/specifications/enterprise-beans/4.0/.

 

Regarding JSR-109, since it is not in Jakarta EE we can refer to the JCP document but I believe the concepts are implemented in Glassfish.
[[[a9879, 30]]] Web Services for Java EE, version 1.3. http://jcp.org/en/jsr/detail?id=109.
can be updated to
[[[a9879, 30]]] Web Services for Java EE™, version 1.4. http://jcp.org/en/jsr/detail?id=109.

Similarly Java Transaction Service is also not in Jakarta EE.
[[[a9858, 9]]] Java™ Transaction Service, version 1.0 (JTS). http://www.oracle.com/technetwork/java/javaee/jts-spec095-1508547.pdf.

Thanks

Hussain

 

From:ejb-dev-bounces@xxxxxxxxxxx<ejb-dev-bounces@xxxxxxxxxxx>On Behalf Of Kevin Sutter
Sent: Tuesday, March 3, 2020 7:21 PM
To: ejb developer discussions <ejb-dev@xxxxxxxxxxx>
Subject: Re: [ejb-dev] Request for review on PR# 74 and 75

 

I reviewed PR #74 yesterday and it looks great.  Looking at PR #75 this morning.  But, since neither myself or Hussain have write access to this repo, we need some assistance to get these merged.  Can we get a quick review, approval, and merge from someone on the EJB team?  Thanks!

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



From:        <Hussain.NM@xxxxxxxxxxxxx>
To:        <ejb-dev@xxxxxxxxxxx>
Date:        02/29/2020 23:14
Subject:        [EXTERNAL] [ejb-dev] Request for review on PR# 74 and 75
Sent by:        ejb-dev-bounces@xxxxxxxxxxx

---

I took a stab at formatting the specification document. I selected chapter 11 Enterprise Bean Environment and made the following changes:

• Change italics to monospace for keywords
• Change link to xref
• Move anchors before section heading
• Add source block for code
• Change header level for subsections
• Add monospace for keywords
• Change curly quotes to straight quotes
• Add ordered and numbered list where applicable
• Added footnotes

Attached the diff for PR# 74

The second PR is for chapter 20 Related Documents. I have converted the custom ID into bibliography with custom label which displays the number. This is done to match with the existing document.

Attached the diff for PR# 75

Please review and let me know if any changes are required.

Thanks
Hussain
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored. [attachment "pr74.patch" deleted by Kevin Sutter/Rochester/IBM] [attachment "pr75.patch" deleted by Kevin Sutter/Rochester/IBM] _______________________________________________
ejb-dev mailing list
ejb-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ejb-dev


This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.
_______________________________________________
ejb-dev mailing list
ejb-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/ejb-dev__;!!GqivPVa7Brio!MbZ1iPrM9K57RxUNURQWXEEoT6gNX4GXb5xwAIsWSwIg5GTQDa9xQp_BG9bwbQUqcA$

_______________________________________________
ejb-dev mailing list
ejb-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ejb-dev

This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored. This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.