zerodds-corba-ccm-ejb
CCM↔EJB-Bridge: CosTransactions↔JTA-UserTransaction-Status,
ConnectorBean-Lifecycle, JNDI↔CosNaming-Glue, Java-CCM-Bean-Stub-
Codegen. no_std + alloc, forbid(unsafe_code). Safety
classification: STANDARD.
Spec-Mapping
| Spec | Abschnitt |
|---|---|
| OMG CCM 4.0 | §16 (CCM↔EJB-Equivalents, ConnectorBean-Lifecycle) |
| OMG Transaction Service 1.4 | §10 (CosTransactions::Status, Coordinator/Resource) |
| JEE JTA 1.3 | §3.2 (javax.transaction.Status Constants) |
| JNDI 1.2 | Sub-Context-Naming |
Was ist drin
tx— bijektives MappingTxStatus↔JtaStatus(alle 10 Werte),TxBridge-Trait,InMemoryTxBridge-Impl fuer Test-Hosting.connector_bean—ConnectorBeanJEE-EJB-3-Modell mit CCM-Lifecycle-Mapping (@PostConstruct,@PreDestroy,@Resource,@TransactionAttribute).stub_gen—generate_bean_stub(component, kind)emittiert<Comp>Bean.javaaus AST-Component (CCM 4.0 Annex A Java-PSM).naming_glue—cos_naming_to_jndi+jndi_to_cos_namingbidirektionales Namespace-Mapping.
Was nicht abgedeckt ist
- JNI-/JVM-Bindings — konkrete Container-Bindings (JBoss EAP, WildFly, GlassFish, Open Liberty) sind Caller-Layer; diese Crate liefert das Mapping-Layer auf Modell-Ebene.
- EJB-Container-Hosting — wir starten keine JVM; der ConnectorBean- Lifecycle wird vom externen JEE-Container getrieben.
Beispiel
use ;
// CosTransactions::Status::Active ↔ JTA STATUS_ACTIVE.
assert_eq!;
Tests
See also
- Architecture
- Components
zerodds-ccm— CCM-Equivalent-IDL-Layer (Modell- Eingabe fuer den Stub-Codegen).