docs(core-spring): document Spring Boot starter + metaobjects.omdb.* properties; finish OSGi removal

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: dmealing

server/java/core-spring/README.md

@@ -2,6 +2,29 @@
 
 This module provides comprehensive Spring Framework integration for MetaObjects, including auto-configuration, dependency injection, and Spring Boot support.
 
+## Spring Boot starter
+
+Add the single starter dependency:
+
+    <dependency>
+        <groupId>com.metaobjects</groupId>
+        <artifactId>metaobjects-spring-boot-starter</artifactId>
+        <version>7.1.1-SNAPSHOT</version>
+    </dependency>
+
+On Spring Boot 3, this auto-configures the metadata-loader registry and — when a
+`DataSource` is present — a transaction-aware `ObjectManagerDB`.
+
+Properties:
+
+| Property | Default | Description |
+|---|---|---|
+| `metaobjects.metadata-sources` | (none) | Loader source URIs/resources. |
+| `metaobjects.omdb.dialect` | (auto) | `postgres`/`mysql`/`mssql`/`oracle`/`derby`. Auto-detected from the DataSource when blank. |
+| `metaobjects.omdb.enforce-transaction` | `false` | Require an active transaction for writes. |
+
+Define your own `ObjectManagerDB` bean to opt out of the autoconfigured one.
+
 ## 🚀 **Quick Start**
 
 ### **Add Dependency**
@@ -416,7 +439,7 @@ Optional<MetaObject> user = metaDataService.findMetaObjectByNameOptional("User")
 - Thread-safe for concurrent access
 
 ### **Memory Management**
-- Uses WeakHashMap patterns for OSGi compatibility
+- Uses WeakHashMap patterns to avoid leaking classloaders
 - Automatic cleanup when Spring context shuts down
 - Minimal memory overhead for Spring integration
 

server/java/core-spring/src/main/java/com/metaobjects/spring/MetaDataService.java

@@ -14,7 +14,7 @@
  * Spring Service wrapper for MetaData operations.
  * 
  * <p>Provides a clean, convenient API for the most common MetaData operations
- * while hiding the complexity of the underlying OSGi-compatible registry system.</p>
+ * while hiding the complexity of the underlying loader registry system.</p>
  * 
  * <p><strong>Usage Examples:</strong></p>
  * <pre>{@code

server/java/core-spring/src/test/java/com/metaobjects/spring/MetaDataSpringIntegrationTest.java

@@ -98,7 +98,7 @@ public void setUp() {
 
     @Test
     public void testMetaDataLoaderRegistryConfiguration() {
-        // Verify registry is configured with OSGi-compatible service registry
+        // Verify registry is configured with the service registry
         assertNotNull("MetaDataLoaderRegistry should be configured", metaDataLoaderRegistry);
 
         // Verify test loader was auto-discovered and registered
@@ -200,13 +200,11 @@ public void testAdvancedRegistryAccess() {
     @Test 
     public void testServiceRegistryFactoryIntegration() {
         // Verify that the auto-configuration uses ServiceRegistryFactory
-        // This ensures OSGi compatibility
-        assertNotNull("Registry should be configured with ServiceRegistryFactory", 
+        assertNotNull("Registry should be configured with ServiceRegistryFactory",
             ServiceRegistryFactory.getDefault());
-        
+
         // The MetaDataLoaderRegistry should be using the default service registry
-        // which auto-detects OSGi vs non-OSGi environments
         Collection<MetaDataLoader> loaders = metaDataLoaderRegistry.getDataLoaders();
-        assertNotNull("Loaders should be accessible via OSGi-compatible registry", loaders);
+        assertNotNull("Loaders should be accessible via the loader registry", loaders);
     }
 }