Difference between revisions of "Talk:EclipseLink/UserGuide/JPA/Basic JPA Development/Caching/Shared and Isolated"

Latest revision as of 10:50, 5 May 2011

References to ELUG removed. See some version of this page from before 5/04/11 to see what they were. Handle at some future date.

@@ Line 1: / Line 1: @@
--- [[User:ben.gelernter.oracle.com|Ben Gelernter]] 5/03/11
+-- [[User:ben.gelernter.oracle.com|Ben Gelernter]] 5/04/11
-: ELUG ref
+: ''References to ELUG removed. See some version of this page from before 5/04/11 to see what they were. Handle at some future date.''
-: I removed this reference to ELUG. Return here to see if this information needs to be brought forward into this doc.
-::Under "Isolated Client Sessions," second bullet:
-:::achieve serializable transaction isolation (see [[Using%20Advanced%20Unit%20of%20Work%20API%20(ELUG)#Isolated Client Session Cache|Isolated Client Session Cache]]);
-::Paragraph between the two notes:
-:::Client sessions can access the data source using a connection pool or an exclusive connection. To use an exclusive connection, acquire the isolated client session using a ConnectionPolicy (see How to Acquire a Client Session that Uses Exclusive Connections). Using an exclusive connection provides improved user-based security for reads and writes. Named queries can also use an exclusive connection (see Configuring Named Query Advanced Options).
-::Right after second note, before "Isolated Client Sessions and Oracle Virtual Private Database (VPD)":
-:::For more information, see the following:
-:::    * Isolated Client Session Limitations
-:::    * How to Acquire an Isolated Client Session
-:::    * Configuring Exclusive Isolated Client Sessions for Virtual Private Database