Java EE Configuration JSR
A mind map/brainstorming repository for the Java EE Configuration JSR.
1. Configuration
1.1. Representations
1.1.1. Map<String, String>
1.1.1.1. Multiple values?
1.1.2. Set-based
1.1.2.1. Addition
1.1.3. Configuration archive
1.1.3.1. Standard packaging type for deploying to application servers
1.2. Mutability
1.3. Way for application to expose slots?
2. Backwards Compatibility
2.1. Deployment descriptors
2.1.1. Simple cases
2.1.1.1. ejb-jar.xml
2.1.2. Tough cases
2.1.2.1. web.xml fragments?
2.1.2.2. Vendor-specific deployment descriptors?
2.1.2.3. Names and IDs
2.1.3. Deployment descriptor identifiers
3. Related JSRs
3.1. JSR 77 (Management)
3.2. JSR 88 (Deployment)
4. Related Technologies
4.1. JNDI
4.2. DeltaSpike configuration
4.3. CDI
4.3.1. Extension?
4.4. Seam Config
4.5. java.util.Preferences
4.6. EJB
4.7. alt-dd
4.8. Annotations JSR
5. Areas
5.1. Management
5.2. Staging
5.2.1. Profiles
5.2.2. Inheritance
5.3. Multitenancy
5.4. Tailoring
6. Packaging and deployment
6.1. Configuration archive
6.1.1. Standardization
7. Boundaries
7.1. Application-to-ConfigurationManager
7.2. ConfigurationManager-interface-to-vendor-supplied-ConfigurationManagerImplementation
7.3. ConfigurationManagerImplementation-to-vendor-implemented-configuration-store
7.4. ConfigurationManagerImplementation-to-vendor-implemented-deployment-descriptor-store
7.5. Configuration-package-to-application-server
7.5.1. Is it important for configuration portability?
7.5.1.1. Configuration portability is paramount, according to Bill Shannon
8. Actors
8.1. Configuration service
8.2. Management tools
8.3. Containers
8.4. Application
8.4.1. Responsible for supplying injection points, querying configuration service for values
8.5. Application Server administrators
8.5.1. Responsible for supplying configurations to the application server
8.6. Customizers/Application Assemblers
8.6.1. Responsible for building configuration archives
9. Configuration providers
9.1. Configuration service
9.1.1. Lookup-based
9.1.1.1. Needed for multitenancy
9.2. @Resource injection?
9.3. Configuration CDI provider
9.3.1. Type-safe injection is hard
10. Scope
10.1. Questions
10.1.1. Management?
10.1.2. Versioning?
10.1.3. Staging?
10.1.4. Standalone?
10.1.5. Mutability
10.1.6. Reloading?
10.1.7. Customization?
11. Use Cases
11.1. Integrate with provisioning tooling
11.2. Retrieve configuration
11.3. Deploy one app under different configurations
11.3.1. Automatic injection
11.4. Decouple configuration information from descriptor location
11.5. I want to specify my own alternate EJB implementation
11.5.1. .car file implications
11.6. I want to specify my own CDI implementation
11.6.1. CDI-123
11.6.2. Seam Solder