Java Transaction Configuration - 1.1
What’s new?
Introducing a brand-new extension dedicated to entry/exit definitions. In order to get accurate transactions with specific definition of entry/exit points and to avoid duplication across extensions.
This simplifies some transactions’ call graph, by removing:
- Entry/end points property on objects
- classes, methods, functions, interfaces objects that are not actual entry/end points
Example of simplification in a transaction
Entry point
On the right, the newly calculated transaction, with 2 nodes removed. The entry point is identified more precisely:
End point
On the right, the newly calculated transaction, with 2 nodes removed, and 3 methods whose end points have been deleted. Only the actual end point remains:
Names of deleted packages and objects
Entry points
| Deleted definition | Extension with new modelisation |
|---|---|
| AWT Screens (Definition based on Classes, interfaces and methods) | Java Presentation Frameworks (UI and View objects) |
| javax.swing (Definition based on Classes, interfaces and methods) | Java Presentation Frameworks (UI and View objects) |
| com.sun.java.swing.plaf.windows (Definition based on Classes, interfaces and methods) | Java Presentation Frameworks (UI and View objects) |
| com.google.gwt.user.client (Definition based on Classes, interfaces and methods) | Google Web Toolkit Framework (UI and Webservice Call via GWT resource services) |
| Servlet (Definition based on Classes, interfaces and methods) | Universal Linker : Exposed Web service via Servelet Opertaions Exposed Web service) |
| org.eclipse.birt.report (Definition based on Classes, interfaces and methods) | Business Intelligence and Reporting Tools : Birt UI |
| freemarker (Definition based on Classes, interfaces and methods) | Apache Freemarker : Service Invocation via Java Freemarker FTL Call |
| com.sun.jersey.api.client (Definition based on Classes, interfaces and methods) | REST Service Calls for Java : Webservice Call via Java resource services |
| org.apache.camel | Apache Camel : Message Queue Publishers & Subscibers |
End points
| Deleted definition | Extension with new modelisation |
|---|---|
| com.ibm.mq (Definition based on Classes, interfaces and methods) | Message Queues Extension: Message Queue Publishers & Subscibers |
| com.ibm.msg (Definition based on Classes, interfaces and methods) | Message Queues Extension:Message Queue Publishers & Subscibers |
| com.ibm.jms (Definition based on Classes, interfaces and methods) | Message Queues Extension :Message Queue Publishers & Subscibers |
| javax.jms (Definition based on Classes, interfaces and methods) | Message Queues Extension :Message Queue Publishers & Subscibers |
| org.apache.activemq (Definition based on Classes, interfaces and methods) | Message Queues Extension :Message Queue Publishers & Subscibers |
| org.springframework.jms (Definition based on Classes, interfaces and methods) | Message Queues Extension :Message Queue Publishers & Subscibers |
| org.springframework.web (Definition based on Classes, interfaces and methods) | Spring MVC Framework: Exposed Web service via Spring MVC Opertaions |
| org.apache.camel (Definition based on Classes, interfaces and methods) | Apache Camel : Message Queue Publishers & Subscibers |
| org.apache.commons.httpclient (Definition based on Classes, interfaces and methods) | REST Service Calls for Java: Webservice Calls via Java Services |
| java.sql (Definition based on Classes, interfaces and methods) | JDBC : SQL queries |
| org.hibernate (Definition based on Classes, interfaces and methods) | Java Persistence Frameworks : SQL queries and Entity operations calling DB tables/Procedures |
| org.springframework.jdbc (Definition based on Classes, interfaces and methods) | Spring Data/JDBC Frameworks: SQL queries and Entity operations calling DB tables/Procedures |
| Query (Definition based on Classes, interfaces and methods) | Java Persistence Frameworks SQL queries and Entity operations calling DB tables/Procedures |
| com.informix.jdbc (Definition based on Classes, interfaces and methods) | JDBC: SQL queries and Entity operations calling DB tables/Procedures |
| net.sourceforge.jtds.jdbc (Definition based on Classes, interfaces and methods) | JDBC: SQL queries and Entity operations calling DB tables/Procedures |
| javax.xml.rpc (Definition based on Classes, interfaces and methods) | JAX-WS : Exposed Web service via JAX-WS Opertaions |
| org.springframework.ws (Definition based on Classes, interfaces and methods) | JAX-WS: Exposed Web service via JAX-WS Opertaions |
Description
This extension defines entry/end points to compute Automated Function Points (ISO/IEC 19515). This is also used to create CAST Imaging Blueprint.
It will be installed automatically as a dependency of JEE Analyzer version ≥ 1.3.18-funcrel.
Transactions
Transaction support is derived from metamodel concepts used to build CAST Imaging Blueprint and structural transaction flows. Entry Points start transactions; Exit Points include both output/boundary concepts and Data Entities manipulated by transactions.
| Role | Support | Breakdown |
|---|---|---|
| Entry Point | No direct concept type details | |
| Exit Point |
|
Data version: 1.1.0-funcrel
ISO 5055 Structural Rules
Quality support is based on ISO 5055 structural rules available for the selected extension version. Counts are grouped by ISO 5055 characteristic.
| Reliability | Maintainability | Security | Performance Efficiency |
|---|---|---|---|
Data version: 1.1.0-funcrel
Compatibility
| JEE Analyzer | Supported |
|---|---|
| ≥ 1.3.18-funcrel | ✅ |
Download and installation instructions
This extension will be downloaded and installed automatically when JEE Analyzer version ≥ 1.3.18-funcrel is installed.