> 9.1.10 Commit options > I guess option A is the answer to your question. If a non-ejb client tries > to access a bean in a transaction it will not be allowed to by the database. It seems that spec "9.1.10 Commit options" allows 3 options. A. exclusive access B. read for update (lock) at the start of the transaction (and unlock at the end of it). C. no caching at all. How do you specify in jBoss which option you elect to apply? Are all three options supported? -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
- RE: [jBoss-User] Any R-O tool's out there? Jay Walters
- RE: [jBoss-User] Any R-O tool's out there? Jon Finanger
- Off topic was RE: [jBoss-User] Any R-O tool's out the... Robert Krueger
- RE: Off topic was RE: [jBoss-User] Any R-O tool's... Jon Finanger
- RE: Off topic was RE: [jBoss-User] Any R-O to... Robert Krueger
- RE: [jBoss-User] Any R-O tool's out there? ERIK . POUPAERT
- RE: [jBoss-User] Any R-O tool's out there? Jon Finanger
- RE: [jBoss-User] Any R-O tool's out there? ERIK . POUPAERT
- RE: [jBoss-User] Any R-O tool's out there? ERIK . POUPAERT
- RE: [jBoss-User] Any R-O tool's out there? Jay Walters
- RE: [jBoss-User] Any R-O tool's out there? Jon Finanger
- RE: [jBoss-User] Any R-O tool's out there? Robert Krueger
- RE: [jBoss-User] Any R-O tool's out there? Jay Walters
