Uploaded image for project: 'Spring Roo'
  1. Spring Roo
  2. ROO-301

Choose between data access patterns

          Details

          • Type: New Feature
          • Status: Resolved
          • Priority: Major
          • Resolution: Complete
          • Affects Version/s: 1.1.4.RELEASE
          • Fix Version/s: 1.2.0.M1
          • Component/s: PERSISTENCE
          • Labels:
            None

            Description

            At this time, the Aspect J generated aspects and entity classes follow the Active Record pattern.

            It would be nice if we could choose between this pattern and Data Access Object, with or without Spring DaoSupport. The way to configure would be "persistence setup ... --databaseAccessPattern ActiveRecord|DAO".

              Attachments

              1. ICriteria.java
                0.3 kB
              2. IFilter.java
                0.2 kB
              3. Repository.java
                0.3 kB

                Issue Links

                depends on

                Task - A task that needs to be done. ROO-2197 Remove dependency on EntityMetadata for Web UI scaffolding add-ons

                • Major - Major loss of function.
                • Resolved

                Improvement - An improvement or enhancement to an existing feature or task. ROO-1372 Joey infrastructure

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Resolved
                is depended on by

                Improvement - An improvement or enhancement to an existing feature or task. ROO-270 Create manual controller and view for non-entity classes

                • Major - Major loss of function.
                • Open
                is duplicated by

                New Feature - A new feature of the product, which has yet to be developed. ROO-394 Roo should facilitate creation of Repository interface and classes as per DDD concepts for domain objects

                • Major - Major loss of function.
                • Closed

                Improvement - An improvement or enhancement to an existing feature or task. ROO-339 Get rid of Active Record pattern and use Repository & Criteria pattern instead

                • Major - Major loss of function.
                • Closed
                is related to

                Sub-task - The sub-task of the issue ROO-340 Introduce Service layer and move all finders to it

                • Major - Major loss of function.
                • Resolved
                relates to

                New Feature - A new feature of the product, which has yet to be developed. ROO-2693 Repository layer support for Spring Data MongoDB

                • Major - Major loss of function.
                • Resolved

                  Activity

                    People

                    • Assignee:
                      sschmidt Stefan Schmidt
                      Reporter:
                      patriarch24 Cyril Delmas
                    • Votes:
                      107 Vote for this issue
                      Watchers:
                      75 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: