OpenJPA
  1. OpenJPA
  2. OPENJPA-417

Support more elements in collections and maps

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.0
    • Component/s: None
    • Labels:
      None

      Description

      It would be useful if OpenJPA could support Map<String,String>, Collection<String>, Map<UserDefinedType,OtherUserDefinedType> etc. more fluently.

        Activity

        Hide
        Albert Lee added a comment -

        We run into a scenario where backward compatibility is required for this feature. To allow existing application to work, the attached patch introduces an option (StoreMapCollectionInEntityAsBlob) in the openjpa.Compatibility plugin which restores the behavior implemented in the previous releases. The default value for the new option is false, that means the current feature implementation will be the default behavior. The new behavior is what we recommend new application to use.

        Please review the patch and comments are welcome.
        Albert Lee.

        Show
        Albert Lee added a comment - We run into a scenario where backward compatibility is required for this feature. To allow existing application to work, the attached patch introduces an option (StoreMapCollectionInEntityAsBlob) in the openjpa.Compatibility plugin which restores the behavior implemented in the previous releases. The default value for the new option is false, that means the current feature implementation will be the default behavior. The new behavior is what we recommend new application to use. Please review the patch and comments are welcome. Albert Lee.
        Hide
        Michael Dick added a comment -

        Hi Albert,

        I took a quick look at the patch and it looks good to me. The convention in the Compatibility class is to use getXxxxx() instead of isXxxxx() though, but that's a rather simple change.

        Show
        Michael Dick added a comment - Hi Albert, I took a quick look at the patch and it looks good to me. The convention in the Compatibility class is to use getXxxxx() instead of isXxxxx() though, but that's a rather simple change.
        Hide
        Tamas Sandor added a comment -

        Hello,

        I'm using the latest v1.1.0 (openjpa-1.1.0-r422266:656510) and it seems, if I specify the joinColumn name, mappingtool does not specify the right column length with varchar2.
        However, if I do not want to rename the joinColumn (and use the generated one), it find the right column length.

        I think it's a minor bug.

        Show
        Tamas Sandor added a comment - Hello, I'm using the latest v1.1.0 (openjpa-1.1.0-r422266:656510) and it seems, if I specify the joinColumn name, mappingtool does not specify the right column length with varchar2. However, if I do not want to rename the joinColumn (and use the generated one), it find the right column length. I think it's a minor bug.

          People

          • Assignee:
            Unassigned
            Reporter:
            Patrick Linskey
          • Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development