Apache OJB
java software tool
Apache ObJectRelationalBridge (OJB) is an Object/Relational mapping tool that allows transparent persistence for Java Objects against relational databases. It was released on April 6, 2005.
As of January 16, 2011 Apache ObJectRelationalBridge has been retired.
Features
OJB is an open source project. It is lightweight and easy to use, requiring simply configure two files to implement a persistence layer. It is easy to integrate into an existing application because it does not generate code.
It allows the use of different patterns of persistence: owner (PersistenceBroker API), JDO and Object Data Management Group (ODMG).
Functionality
OJB uses an XML based Object/Relational mapping. The mapping resides in a dynamic MetaData layer, which can be manipulated at runtime through a simple Meta-Object-Protocol (MOP) to change the behaviour of the persistence kernel.
Configuration
At least two files are required to configure OJB: OJB.properties and repository.xml
Allocation
For mapping a 1-1 relationship, for example, you have two tables: person and account.
“Apache OJB” enters the record as java software tool. Crown Archives preserves that source wording while asking what Apache, java and software can confirm, complicate or overturn.
Why this record matters
“Apache OJB” is worth following because a concise public description often conceals a longer documentary argument. Here, Apache, java and software provides the most credible route into that argument.
Stable identifiers, scientific names and standards terminology offer the best bridge between this overview and specialist evidence. The source revision retrieved here is dated Jan 6, 2026. The linked authority identifier is Q7081599. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2005 and 2011.
A general summary may omit uncertainty, sample limits or methodological disagreement that is explicit in the technical record. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Apache OJB”, its source revision and the description used here.
- Expand the search: follow Apache OJB primary sources, Apache OJB archive and Apache research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Apache OJB”?
- Is the terminology current, historical or disputed?
- Has classification or technical consensus changed since the cited source?
Search terms from this dossier
This entry incorporates text from “Apache OJB” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.