Java Transaction API
E200588
Java Transaction API is a Java specification that provides a standard interface for managing distributed transactions across multiple resources in enterprise applications.
All labels observed (4)
| Label | Occurrences |
|---|---|
| Java Transaction API canonical | 3 |
| TransactionManager | 1 |
| jakarta.transaction API in Jakarta EE | 1 |
| javax.transaction.TransactionSynchronizationRegistry | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1793509 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Java Transaction API Context triple: [EJB container, integratesWith, Java Transaction API]
-
A.
JDBC
JDBC (Java Database Connectivity) is a Java-based API that enables applications to connect to and interact with relational databases in a standardized way.
-
B.
JMS
JMS (Java Message Service) is a Java API specification that enables applications to create, send, receive, and read messages in a loosely coupled, asynchronous, and reliable messaging system.
-
C.
Jakarta EE
Jakarta EE is a set of specifications that extend the Java SE platform for enterprise-level applications, defining standard APIs for building scalable, secure, and portable Java-based enterprise software.
-
D.
Java Platform, Standard Edition
Java Platform, Standard Edition (Java SE) is the core Java computing platform that provides the fundamental libraries, virtual machine, and tools for developing and running general-purpose Java applications on desktops and servers.
-
E.
EJB container
An EJB container is a server-side runtime environment in Java EE application servers that manages the lifecycle, security, transactions, and remote access of Enterprise JavaBeans components.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Java Transaction API Target entity description: Java Transaction API is a Java specification that provides a standard interface for managing distributed transactions across multiple resources in enterprise applications.
-
A.
JDBC
JDBC (Java Database Connectivity) is a Java-based API that enables applications to connect to and interact with relational databases in a standardized way.
-
B.
JMS
JMS (Java Message Service) is a Java API specification that enables applications to create, send, receive, and read messages in a loosely coupled, asynchronous, and reliable messaging system.
-
C.
Jakarta EE
Jakarta EE is a set of specifications that extend the Java SE platform for enterprise-level applications, defining standard APIs for building scalable, secure, and portable Java-based enterprise software.
-
D.
Java Platform, Standard Edition
Java Platform, Standard Edition (Java SE) is the core Java computing platform that provides the fundamental libraries, virtual machine, and tools for developing and running general-purpose Java applications on desktops and servers.
-
E.
EJB container
An EJB container is a server-side runtime environment in Java EE application servers that manages the lifecycle, security, transactions, and remote access of Enterprise JavaBeans components.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Java specification
ⓘ
transaction management API ⓘ |
| abbreviation | JTA ⓘ |
| category | middleware technology ⓘ |
| currentName | Jakarta Transactions ⓘ |
| currentPackage |
jakarta.transaction
ⓘ
linked to:
Jakarta Transactions
|
| definedIn |
JSR 907
ⓘ
linked to:
JSR
|
| domain |
distributed transactions
ⓘ
enterprise applications ⓘ |
| enables |
coordination of transactions across databases and message queues
ⓘ
two-phase commit across multiple resources ⓘ |
| governedBy | Java Community Process ⓘ |
| hasComponent |
javax.transaction.Transaction
ⓘ
javax.transaction.TransactionManager ⓘ javax.transaction.TransactionSynchronizationRegistry ⓘ
linked to:
Java Transaction API
javax.transaction.UserTransaction ⓘ
linked to:
Jakarta Transactions
javax.transaction.xa.XAResource ⓘ |
| hasGoal |
interoperability between transaction managers and resource managers
ⓘ
portability of transactional applications across vendors ⓘ |
| integratesWith |
EJB container
ⓘ
JDBC XA drivers ⓘ JPA ⓘ
linked to:
Java Persistence API
Java EE container-managed transactions ⓘ |
| laterMaintainedBy | Oracle Corporation ⓘ |
| originallyMaintainedBy | Sun Microsystems ⓘ |
| package |
javax.transaction
ⓘ
javax.transaction.xa ⓘ |
| partOf |
Jakarta EE platform
ⓘ
linked to:
Jakarta EE
Java EE platform ⓘ
linked to:
Java EE
|
| provides |
APIs for demarcating transactions
ⓘ
APIs for transaction status inquiry ⓘ APIs for transaction synchronization ⓘ standard interface for transaction management ⓘ |
| separates | application code from transaction management details ⓘ |
| specifies |
rollback rules
ⓘ
synchronization callbacks ⓘ transaction timeouts ⓘ |
| standardizedBy | JSR specification process ⓘ |
| supports |
XA transactions
ⓘ
distributed transactions across multiple resources ⓘ global transactions ⓘ |
| supportsProgrammingModel |
declarative transaction demarcation
ⓘ
programmatic transaction demarcation ⓘ |
| usedBy |
Jakarta EE containers
ⓘ
application servers ⓘ enterprise Java applications ⓘ |
| usedFor | ensuring ACID properties in distributed systems ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Java Transaction API Description of subject: Java Transaction API is a Java specification that provides a standard interface for managing distributed transactions across multiple resources in enterprise applications.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: Java Transaction API
linked to: Java Transaction API
linked to: Java Transaction API