Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-87

Seam managed EBJ3 Query

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      Have Seam provide a bridge between EBJ3 Query's, multiple requests, and the UI for purposes of efficient query result paging, large collection handling, etc. The Seam developer could simply be concerned with setting up and returning an EJB3 Query object from a getter. The Query at that point represents a sort of "meta collection". From that point on, Seam and JSF components would manage how it best makes sense to execute (and re-execute) the query, including setFirstResult/setMaxResults, according to changing demands of the application and/or UI components.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                gavin.king Gavin King
                Reporter:
                rdewell ryan dewell
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: