Spring Roo
  1. Spring Roo
  2. ROO-889

Implement relationship properties and partial DTOs

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Complete
    • Affects Version/s: 1.1.0.M1
    • Fix Version/s: 1.1.0.M3
    • Component/s: GWT
    • Labels:
      None

      Description

      Per the "Sparsely populated records" section of https://wave.google.com/wave/#restored:search:jira,restored:wave:googlewave.com!w%252BWU4iAICkI.1, this must be possible:

      Range range = table.getRange();
      requestFactory.employeeRequest()
      .findEmployeeEntries(range.getStart(), range.getLength())
      .with("name")
      .with("supervisor.name")
      .fire(new Receiver<List<Employee>>()

      { ... }

      );

      Remember to handle List<SomeEntity> as well.

      Ideally this will include throwing runtime exceptions when client code calls the getter for an unrequested property, but perhaps that will need to be spun off to a separate M3 task.

        Issue Links

          Activity

          Hide
          Ganesh Krishnan added a comment -

          This should not be a "Minor Improvement". For building Google AppEngine applications this is blocking me from using ROO to build entities with relationships. Even modifying the code results in error since Roo uses Long for primary key and Google AppEngine BigTable does not allow the owned child to have a primary key that is of type Long. The way out is to refactor your code to remove ROO and then modify the primary key to use Encoded String or Key.

          Showstopper.

          Show
          Ganesh Krishnan added a comment - This should not be a "Minor Improvement". For building Google AppEngine applications this is blocking me from using ROO to build entities with relationships. Even modifying the code results in error since Roo uses Long for primary key and Google AppEngine BigTable does not allow the owned child to have a primary key that is of type Long. The way out is to refactor your code to remove ROO and then modify the primary key to use Encoded String or Key. Showstopper.
          Hide
          Arash added a comment -

          This is still an issue as of M3!!! This jira is encompassing all 912, 902 and 1079 and marked as resolved for M3 but SetRecord and ListRecord do not exist in generated gwt application hence causing build issues.

          Show
          Arash added a comment - This is still an issue as of M3!!! This jira is encompassing all 912, 902 and 1079 and marked as resolved for M3 but SetRecord and ListRecord do not exist in generated gwt application hence causing build issues.
          Hide
          Simon Whelan added a comment -

          The status of this ticket is resolved, but its still an issue with M3. Did this make it into M3?...if not when should we expect it...thanks

          Show
          Simon Whelan added a comment - The status of this ticket is resolved, but its still an issue with M3. Did this make it into M3?...if not when should we expect it...thanks
          Hide
          Yuri added a comment -

          I'm still getting an error in 1.1.0.M3 / STS 2.5.0.M3 / GWT 2.1.0 M3 when trying to add the one side of one-to-many relationship. There is no error until gwt setup is called, but once GWT is setup the error shows up.

          Please help, this is not a minor issue and it does not seem to be fixed in 1.1.0.M3.

          Show
          Yuri added a comment - I'm still getting an error in 1.1.0.M3 / STS 2.5.0.M3 / GWT 2.1.0 M3 when trying to add the one side of one-to-many relationship. There is no error until gwt setup is called, but once GWT is setup the error shows up. Please help, this is not a minor issue and it does not seem to be fixed in 1.1.0.M3.
          Hide
          Raul Martinez added a comment -

          I confirm that the error still occurs in version 1.1.0.M3 in each command "field set" launched to build relationships ONE TO MANY or MANY TO MANY.

          Solve this is important because otherwise the use of ROO with GWT would be quite limited...

          Show
          Raul Martinez added a comment - I confirm that the error still occurs in version 1.1.0.M3 in each command "field set" launched to build relationships ONE TO MANY or MANY TO MANY. Solve this is important because otherwise the use of ROO with GWT would be quite limited...
          Hide
          Ray Cromwell added a comment -

          Sets and Lists are supported in RC1, not M3

          Show
          Ray Cromwell added a comment - Sets and Lists are supported in RC1, not M3
          Hide
          Ganesh Krishnan added a comment -

          There appears to be no RC1 candidate for the 1.1.x releases.
          Or are you talking about the 1.0.0 RC1 release?

          Show
          Ganesh Krishnan added a comment - There appears to be no RC1 candidate for the 1.1.x releases. Or are you talking about the 1.0.0 RC1 release?

            People

            • Assignee:
              Ray Cromwell
              Reporter:
              Chris Ramsdale
            • Votes:
              7 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: