[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakarta.ee-spec.committee] Suggested Jakarta EE Specifictaion Naming standard
|
I have raised the name question on the CDI developer list.
On Wed, Apr 17, 2019 at 2:20 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
>
> +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.
