Details

    • Type: Sub-task Sub-task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: 1.1.4.RELEASE
    • Fix Version/s: 1.2.0.M1
    • Component/s: GENERAL OBJECTS
    • Labels:
      None

      Description

      Introduce Service layer and move all finders to it. As a continuation of ROO-301/339, a service layer can be introduced that hides from controllers the use of DAOs. All finder methods should be moved to the services layer along with the CRUD methods.

        Issue Links

          Activity

          Hide
          Neal Ravindran added a comment -

          That is excellent. Only problem would be that it would be tedious to do in a onsy-twosy fashion and defeat the RAD principle of Roo. Can gvnix automate the creation of services by moving all finders into the services layer which would delegate to the finder methods created when doing DBRE? That capable of generating the 3 layers out of the box would have great value, imo.

          Show
          Neal Ravindran added a comment - That is excellent. Only problem would be that it would be tedious to do in a onsy-twosy fashion and defeat the RAD principle of Roo. Can gvnix automate the creation of services by moving all finders into the services layer which would delegate to the finder methods created when doing DBRE? That capable of generating the 3 layers out of the box would have great value, imo.

          The services add-on can create local service classes and operations on it, but can not move methods. The methods can then be published as Web services.

          On the other hand, the services add-on can import remote web services as local service classes.

          Also you can create Web services from a WSDL definition format.

          Finally, the new version we are developing allow you to import some web service with security features.

          Show
          Mario Martínez Sánchez - gvNIX - DiSiD Technologies S.L. added a comment - The services add-on can create local service classes and operations on it, but can not move methods. The methods can then be published as Web services. On the other hand, the services add-on can import remote web services as local service classes. Also you can create Web services from a WSDL definition format. Finally, the new version we are developing allow you to import some web service with security features.
          Hide
          Enrique Ruiz (DiSiD) added a comment -

          Stefan, please take in account https://jira.springsource.org/browse/ROO-2103, hope it helps for this issue.

          Show
          Enrique Ruiz (DiSiD) added a comment - Stefan, please take in account https://jira.springsource.org/browse/ROO-2103 , hope it helps for this issue.
          Hide
          Enrique Ruiz (DiSiD) added a comment -

          Neal, it is a good idea that will let us to use the Criteria Builder API (https://jira.springsource.org/browse/ROO-2112), but gvNIX cannot be ahead of Roo, so we have to wait Stefan solves this issue to know what Roo provides and what gvNIX can do.

          Indeed, Stefan, Alan can you advance us any tech design info about how you will solve this issue?

          Thanks!

          Show
          Enrique Ruiz (DiSiD) added a comment - Neal, it is a good idea that will let us to use the Criteria Builder API ( https://jira.springsource.org/browse/ROO-2112 ), but gvNIX cannot be ahead of Roo, so we have to wait Stefan solves this issue to know what Roo provides and what gvNIX can do. Indeed, Stefan, Alan can you advance us any tech design info about how you will solve this issue? Thanks!
          Hide
          Stefan Schmidt added a comment -

          With the upcoming Roo 1.2.0.M1 release Roo will offer support for service layers (documentation to be published with the 1.2.0.M1 release). As part of this effort a new @RooService annotation and a new 'service' command will be offered (see http://static.springsource.org/spring-roo/reference/html-single/index.html#command-index-service for details).

          The request for dynamic finder integration for service layers (and repository layers) has been moved to ROO-2694 to allow separate tracking.

          Show
          Stefan Schmidt added a comment - With the upcoming Roo 1.2.0.M1 release Roo will offer support for service layers (documentation to be published with the 1.2.0.M1 release). As part of this effort a new @RooService annotation and a new 'service' command will be offered (see http://static.springsource.org/spring-roo/reference/html-single/index.html#command-index-service for details). The request for dynamic finder integration for service layers (and repository layers) has been moved to ROO-2694 to allow separate tracking.

            People

            • Assignee:
              Stefan Schmidt
              Reporter:
              Alexander Makarevitch
            • Votes:
              55 Vote for this issue
              Watchers:
              44 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: