Add Jakarta EE Feature Recommendations section

[glassfishrobot]

Add a section explaining higher level Java EE feature choices and recommendations as they pertain to the application (e.g. annotations vs. XML). Need to maintain a balance since API/feature best practices are not the primary focus (as opposed to architectural blueprints/patterns) and the application would not cover large parts of many APIs (as perhaps the samples do).

Alternatively, create API specific sub-projects (or altogether separate projects perhaps leveraging this code base) that focus on technology feature choices/best practices (e.g. best practices for WebSocket, JAX-RS, JPA, EJB, JMS, etc).

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/cargotracker/issues/20
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot

[glassfishrobot]

@glassfishrobot Commented Reported by reza_rahman

[glassfishrobot]

@glassfishrobot Commented Was assigned to reza_rahman

[glassfishrobot]

@glassfishrobot Commented This issue was imported from java.net JIRA CARGOTRACKER-20

[m-reza-rahman]

Closing as part of cleanup as too low priority for the foreseeable future.