Java EE Configuration JSR

1. Actors

1.1. Configuration service

1.2. Management tools

1.3. Containers

1.4. Application

1.4.1. Responsible for supplying injection points, querying configuration service for values

1.5. Application Server administrators

1.5.1. Responsible for supplying configurations to the application server

1.6. Customizers/Application Assemblers

1.6.1. Responsible for building configuration archives

2. Configuration providers

2.1. Configuration service

2.1.1. Lookup-based

2.1.1.1. Needed for multitenancy

2.2. @Resource injection?

2.3. Configuration CDI provider

2.3.1. Type-safe injection is hard

3. Configuration

3.1. Representations

3.1.1. Map<String, String>

3.1.1.1. Multiple values?

3.1.2. Set-based

3.1.2.1. Addition

3.1.3. Configuration archive

3.1.3.1. Standard packaging type for deploying to application servers

3.2. Mutability

3.3. Way for application to expose slots?

4. Backwards Compatibility

4.1. Deployment descriptors

4.1.1. Simple cases

4.1.1.1. ejb-jar.xml

4.1.2. Tough cases

4.1.2.1. web.xml fragments?

4.1.2.2. Vendor-specific deployment descriptors?

4.1.2.3. Names and IDs

4.1.3. Deployment descriptor identifiers

5. Scope

5.1. Questions

5.1.1. Management?

5.1.2. Versioning?

5.1.3. Staging?

5.1.4. Standalone?

5.1.5. Mutability

5.1.6. Reloading?

5.1.7. Customization?

6. Related JSRs

6.1. JSR 77 (Management)

6.2. JSR 88 (Deployment)

7. Related Technologies

7.1. JNDI

7.2. DeltaSpike configuration

7.3. CDI

7.3.1. Extension?

7.4. Seam Config

7.5. java.util.Preferences

7.6. EJB

7.7. alt-dd

7.8. Annotations JSR

8. Areas

8.1. Management

8.2. Staging

8.2.1. Profiles

8.2.2. Inheritance

8.3. Multitenancy

8.4. Tailoring

9. Use Cases

9.1. Integrate with provisioning tooling

9.2. Retrieve configuration

9.3. Deploy one app under different configurations

9.3.1. Automatic injection

9.4. Decouple configuration information from descriptor location

9.5. I want to specify my own alternate EJB implementation

9.5.1. .car file implications

9.6. I want to specify my own CDI implementation

9.6.1. CDI-123

9.6.2. Seam Solder

10. Wild ideas

10.1. Special classloader

11. Packaging and deployment

11.1. Configuration archive

11.1.1. Standardization

12. Boundaries

12.1. Application-to-ConfigurationManager

12.2. ConfigurationManager-interface-to-vendor-supplied-ConfigurationManagerImplementation

12.3. ConfigurationManagerImplementation-to-vendor-implemented-configuration-store

12.4. ConfigurationManagerImplementation-to-vendor-implemented-deployment-descriptor-store

12.5. Configuration-package-to-application-server

12.5.1. Is it important for configuration portability?

12.5.1.1. Configuration portability is paramount, according to Bill Shannon