OpenJPA
  1. OpenJPA
  2. OPENJPA-293

OpenJPA should not require managed type enhancement

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.9.0, 0.9.6, 0.9.7
    • Fix Version/s: None
    • Component/s: docs, kernel, UnenhancedClasses
    • Labels:
      None

      Description

      OpenJPA currently requires a post-compilation / deploy-time class processing step. This should be made optional.

      1. OPENJPA-293.patch
        221 kB
        Patrick Linskey

        Issue Links

          Activity

          Hide
          Patrick Linskey added a comment -

          I have since modified the patch to automatically disable detached state if a class does not have a DetachedState field specified. This differs from the enhancement contract default, which will put a synthetic detached state in place if none is specified and @DetachedState(enabled=false) is not specified.

          Show
          Patrick Linskey added a comment - I have since modified the patch to automatically disable detached state if a class does not have a DetachedState field specified. This differs from the enhancement contract default, which will put a synthetic detached state in place if none is specified and @DetachedState(enabled=false) is not specified.
          Hide
          Patrick Linskey added a comment -

          Patch to make enhancement optional. This feature is pretty experimental, but the only significant code changes are to the enhancer. For enhanced classes, code pathways should remain virtually unchanged.

          Lazy loading in non-redefined types is currently not behaving correctly, and I have not yet run the CTS in any configuration (including with enhancement) yet.

          To do:

          • resolve issues marked with '#####' in patch
          • lazy loading in field-access without redefinition
          • clearing in pnew property-access without redefinition
          • figure out how to auto-test the redefinition code, either in Java 5 or in Java 6
          • test compound primary keys
          • run CTS in the following combinations:
          • Java 6
          • Java 5 with javaagent
          • Java 5 without javaagent
          Show
          Patrick Linskey added a comment - Patch to make enhancement optional. This feature is pretty experimental, but the only significant code changes are to the enhancer. For enhanced classes, code pathways should remain virtually unchanged. Lazy loading in non-redefined types is currently not behaving correctly, and I have not yet run the CTS in any configuration (including with enhancement) yet. To do: resolve issues marked with '#####' in patch lazy loading in field-access without redefinition clearing in pnew property-access without redefinition figure out how to auto-test the redefinition code, either in Java 5 or in Java 6 test compound primary keys run CTS in the following combinations: Java 6 Java 5 with javaagent Java 5 without javaagent

            People

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

              Dates

              • Created:
                Updated:

                Development