User: danch
Date: 01/06/12 23:52:18
Modified: src/resources/org/jboss/metadata jaws.dtd
Log:
second pass at collection finder optimization - this fixes problem with defined
finders doing joins
Revision Changes Path
1.5 +3 -1 jboss/src/resources/org/jboss/metadata/jaws.dtd
Index: jaws.dtd
===================================================================
RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/metadata/jaws.dtd,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- jaws.dtd 2001/05/29 22:02:58 1.4
+++ jaws.dtd 2001/06/13 06:52:18 1.5
@@ -53,7 +53,9 @@
a specific ordering. it must contain name and query elements and my contain
1 order element.
After JBoss version 2.3, it may contain a read-ahead element indicating whether
- or not all data for the entities selected should be loaded immediatly. -->
+ or not all data for the entities selected should be loaded immediatly. Note
+ that JAWS/JBoss cannot guarentee serializable transactions with the read-ahead
+ option!-->
<!ELEMENT finder (name,query,order?,read-ahead?)>
<!-- the name within a finder element must contain the name of the finder
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
