Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.0.RC1
    • Component/s: GWT
    • Labels:
      None

      Description

      This must be considered in tandem with the need for a general find method on RequestFactory (https://jira.springsource.org/browse/ROO-1244), and the desire to have non-proxies in update events. The solution is probably something like:

      interface Proxy {
      ProxyId toId(); // Encapsulates type and id. Name does not conflict with getter properties
      }

      There is no need for ProxyId to be an interface. For that matter, it might not need to have any public methods

      RecordChangeEvent#getRecord() becomes RecordChangeEvent#getProxyId() instead

      Implement RequestFactory#find(ProxyId)

      Perhaps the future-id-aware equality gymnastics needed by https://jira.springsource.org/browse/ROO-1240 could also be embodied by ProxyId?

        Activity

        Hide
        Ray Ryan added a comment -

        Refocussing this to deal strictly with getId() (we've decided our need for getVersion() is unclear, separate issue to follow), and moving it to the m3 list. We can live with the status quo a bit longer.

        Show
        Ray Ryan added a comment - Refocussing this to deal strictly with getId() (we've decided our need for getVersion() is unclear, separate issue to follow), and moving it to the m3 list. We can live with the status quo a bit longer.
        Hide
        Ray Ryan added a comment -

        Narrowed the scope of this. We will support Long and String keys. Composite key users will have to serialize their objects to and from String.

        There is a slim chance that methods other than getId() will be able to serve as the key property (via an @Id annotation), but it is not guaranteed. If that cannot happen, we need to remember to delete the @Id annotation, it's noise.

        Show
        Ray Ryan added a comment - Narrowed the scope of this. We will support Long and String keys. Composite key users will have to serialize their objects to and from String. There is a slim chance that methods other than getId() will be able to serve as the key property (via an @Id annotation), but it is not guaranteed. If that cannot happen, we need to remember to delete the @Id annotation, it's noise.
        Hide
        Bryan Keller added a comment -

        Will there be a straightforward way to use UUIDs as keys in GWT in addition to String and Long types? Perhaps this could be done by registering a converter with a conversion service, much like you can do with Spring MVC and the IdToEntityConverter class.

        Show
        Bryan Keller added a comment - Will there be a straightforward way to use UUIDs as keys in GWT in addition to String and Long types? Perhaps this could be done by registering a converter with a conversion service, much like you can do with Spring MVC and the IdToEntityConverter class.

          People

          • Assignee:
            Stephanie Brubaker
            Reporter:
            Ray Ryan
          • Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 1d
              1d
              Remaining:
              Remaining Estimate - 1d
              1d
              Logged:
              Time Spent - Not Specified
              Not Specified