Differences

This shows you the differences between two versions of the page.

--- at-m42:lecture14 [2009/04/26 10:07] – eechris
+++ at-m42:lecture14 [2009/04/26 10:14] – eechris
@@ Line 584: / Line 584: @@
   * Better to use an existing framework. Many available!
   * All implement //Data Mapper//, //Query Object// and //Unit of Work// patterns to provide **Transparent Persistence** for Java objects.
 ----
@@ Line 627: / Line 628: @@
   * For Java programmers ORM has the advantage of keeping SQL out of the code. But that is why we have DB architects!
 ===== Lecture Contents =====
-  * **[[#What is a Relational Database?|An introduction to relational databases and SQL]]**
+  * [[#What is a Relational Database?|An introduction to relational databases and SQL]]
   * [[#The Trouble with Databases|JDBC -- Java database connectivity API]]
-  * [[Immortal Objects]]
+  * [[#Immortal Objects]]
-  * [[Persistence Patterns]]
+  * [[#Persistence Patterns]]
-  * [[Other forms of Enterprise Integration]]
+  * **[[#Other forms of Enterprise Integration]]**
 ===== Other Forms of Enterprise Integration =====
   * Enterprise integration is not just about databases and SQL.
-  * Enterprise information systems such as:
+  * Enterprise information systms also often have to be built in to enterprise applications.
+  * Main technologies for this form of integration is the Java Connectivity API and Web Services.
+  * May not be talking Java so CORBA and similar technologies may come into play.
+----
+Some examples of enterprise information systems are:
   * Human Resources Systems
   * Payroll systems
@@ Line 645: / Line 654: @@
   * Business to Business Systems
   * Enterprise communication systems
-  * Other "legacy” systems
+  * Other //so-called// "legacy" systems
-  * 	also often have to be built in to enterprise applications.
-  * Main technologies are the Java Connectivity API and Web Services.
-  * May not be talking Java so CORBA and similar technologies come into play.
 ===== Lecture Summary =====