Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Component/s: Development, JPA, Roadmap
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-11350Need support for anonymous access with JPA
      KULRICE-11177Need JPA related caching functionality to improve performance and support clustering
      KULRICE-9336Replace core.framework.persistence.jpa.criteria package with native JPA Criteria and Query objects
      KULRICE-3914Materializing JPA/Hibernate queries causes strange exception
      KULRICE-6014JPA Conversion Guide
      KULRICE-3720 Need support on lookups to customize help location
      KULRICE-5245Fix context selection so that it can query on multiple attributes
      KULRICE-2360Update LookupUtils for JPA
      KULRICE-12642Differences in the way wildcard querys work between JPA and OJB
      KULRICE-13165Order By not being translated to query in JPA translator
    • Epic Link:
    • Application Requirement:
      KC
    • Sprint:
      2.4.0-m4 JPA Sprint 1
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      OJB had support for query customizers and JPA currently lacks this functionality. Eclipse Link has a custom @Customizer annotation that does this but it would be nice to have something that is provider agnostic so that it can be used across various ORMs.

        Activity

        Hide
        Eric Westfall added a comment -

        Add QueryCustomizer annotation that takes an attributeName, operator(optional defaults to =), value, or valueClass. Chain these together in a concurrent hash map as there can be multiple per descriptor. After setup call each customizer in a chain to customize the class descriptors . In a generic QueryCustomizerBase modify the class descriptor as defined in the query customizer annotation.

        Show
        Eric Westfall added a comment - Add QueryCustomizer annotation that takes an attributeName, operator(optional defaults to =), value, or valueClass. Chain these together in a concurrent hash map as there can be multiple per descriptor. After setup call each customizer in a chain to customize the class descriptors . In a generic QueryCustomizerBase modify the class descriptor as defined in the query customizer annotation.

          People

          • Assignee:
            Allen Fox (Inactive)
            Reporter:
            Gayathri Athreya
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

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

                Agile

                  Structure Helper Panel