Skip Headers

# Using Cursors and Streams With EJB Finders

Previous

Next

Large result sets can be resource-intensive to collect and process. To give the client more control over the returned results, configure TopLink finders to use cursors. This combines TopLink's `CursoredStream` with the ability of the database to cursor data, and breaks up the result set into smaller, more manageable pieces.

Note: If you use the transactional attribute `REQUIRED` for an entity bean, wrap all read operations in `UserTransaction` methods `begin` and `commit` to ensure that read operations beyond the first page of the cursor have a transaction in which to work.