Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Suggested Jakarta EE SpecifictaionNaming standard

Ivar,

 

+1 on most, I’m just wondering how the omnipresent „CDI“ could get accepted as „Jakarta Contexts“ only, there has never been a package „cdi“, but the „context“ part is significantly smaller than the „Inject“.

 

Also what About JSR 330, would that remain javax.inject or also get moved over to „Jakarta“?

 

Werner

 

Sent from Mail for Windows 10

 

From: Bill Shannon
Sent: Wednesday, April 17, 2019 23:26
To: Jakarta specification committee; Ivar Grimstad
Subject: Re: [jakarta.ee-spec.committee] Suggested Jakarta EE SpecifictaionNaming standard

 

+1

Still, the question is just how far to simplify the names.  Going beyond what Wayne proposed we could have:

  • Jakarta XML Messaging
  • Jakarta XML Binding
  • Jakarta XML Web Services
  • Jakarta Common Annotations
  • Jakarta Enterprise Beans
  • Jakarta Persistence
  • Jakarta Contexts and Dependency Injection
  • Jakarta EE Platform
  • Jakarta JSON Binding
  • Jakarta Servlet
  • Jakarta RESTful Web Services
  • Jakarta Server Faces
  • Jakarta JSON Processing
  • Jakarta Security
  • Jakarta Bean Validation
  • Jakarta Mail
  • Jakarta Beans Activation
  • Jakarta Debugging Support for Other Languages
  • Jakarta Server Pages Standard Tag Library
  • Jakarta EE Platform Management
  • Jakarta EE Platform Application Deployment
  • Jakarta XML Registries
  • Jakarta XML-based RPC
  • Jakarta Enterprise Web Services
  • Jakarta Authorization
  • Jakarta Web Services Metadata
  • Jakarta Authentication
  • Jakarta Concurrency Utilities
  • Jakarta Server Pages
  • Jakarta Connectors Architecture
  • Jakarta Dependency Injection
  • Jakarta _expression_ Language
  • Jakarta Messaging Service
  • Jakarta Batch
  • Jakarta WebSocket
  • Jakarta Transaction

A possible concern is that results in some very general names like Management, Deployment, Messaging, Validation, Security, Authentication, etc.  The scope statements for the projects would need to constrain the projects appropriately.

Ivar Grimstad wrote on 4/17/19 9:24 AM:

Suggested naming standard (taken from Wayne's blog post [1]) to send out to the projects. Please comment, simplify, suggest or simply +1 it.

Ivar

§  Replace “Java” with “Jakarta” (e.g. “Java Message Service” becomes “Jakarta Message Service”)

§  Add a space in cases where names are mashed together (e.g. “JavaMail” becomes “Jakarta Mail”)

§  Add “Jakarta” when it is missing (e.g. “_expression_ Language” becomes “Jakarta _expression_ Language”)

§  Rework names to consistently start with “Jakarta” (“Enterprise JavaBeans” becomes “Jakarta Enterprise Beans”)

§  Simplify/shorten names by removing words that do not add value (e.g. "Jakarta Message Service" becomes "Jakarta Messaging" and "Jakarta Servlet API" becomes "Jakarta Servlet")



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

 

 

Back to the top