zerodds-corba-ccm-ejb 1.0.0-rc.1

CCM↔EJB-Bridge: CosTransactions↔JTA-UserTransaction-Status, ConnectorBean-Lifecycle, JNDI↔CosNaming-Glue, Java-CCM-Bean-Stub-Codegen (CCM 4.0 §16 + JEE-JTA-1.3-§3.2). no_std + alloc.
Documentation
  • Coverage
  • 100%
    71 out of 71 items documented1 out of 33 items with examples
  • Size
  • Source code size: 38.94 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 1 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 21s Average build duration of successful builds.
  • all releases: 21s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Homepage
  • zero-objects/zero-dds
    2 1 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • SandraK82

zerodds-corba-ccm-ejb

License: Apache-2.0 docs.rs

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 Mapping TxStatusJtaStatus (alle 10 Werte), TxBridge-Trait, InMemoryTxBridge-Impl fuer Test-Hosting.
  • connector_beanConnectorBean JEE-EJB-3-Modell mit CCM-Lifecycle-Mapping (@PostConstruct, @PreDestroy, @Resource, @TransactionAttribute).
  • stub_gengenerate_bean_stub(component, kind) emittiert <Comp>Bean.java aus AST-Component (CCM 4.0 Annex A Java-PSM).
  • naming_gluecos_naming_to_jndi + jndi_to_cos_naming bidirektionales 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 zerodds_corba_ccm_ejb::{JtaStatus, TxStatus, jta_status_from_cos};

// CosTransactions::Status::Active ↔ JTA STATUS_ACTIVE.
assert_eq!(jta_status_from_cos(TxStatus::Active), JtaStatus::Active);

Tests

cargo test -p zerodds-corba-ccm-ejb

See also