Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.0
    • Fix Version/s: 1.1-JPA
    • Component/s: Documentation
    • Labels:
      None
    • Similar issues:
      KULRICE-9361KNS to KRAD Conversion Guide
      KULRICE-10127Create section in document for conversion from KNS+OJB to KRAD+JPA
      KULRICE-9923Conversion Guide: Multi Value Lookup
      KULRICE-9924Conversion Guide: Other Lookup Features
      KULRICE-10543Verification of Inquiry Conversion Guide
      KULRICE-11561Check that Lookup conversion guide and conversion scripts are up to date
      KULRICE-11562Check that Inquiry conversion guide and conversion scripts are up to date
      KULRICE-11563Check that Maintenance conversion guide and conversion scripts are up to date
      KULRICE-3876JPA - Convert KEW to use JPA
      KULRICE-10120Attribute Definition: Conversion Guide

      Description

      • Just a general comment - this document needs to be written not only for a target audience that includes the KFS and KC projects, but also any existing Rice client applications that are out there in the wild
      • Include just a general overview of why we are making the change, what JPA is, information on the default implementation we are using
      • reference that we were hoping to use JPA 2.0 but it won't be available
      • document that we are dropping support for OJB so this is an impacting and forced upgrade
      • Have a quick introduction with some examples of how to map objects in JPA and what the different annotations are that we are likely to use
        • also need to document any custom annotations and the vendor specific ones that we are using
      • Document the difference between OJB and JPA and how they need to be handled
        • store and persist/merge difference
        • if you don't want a field to be persisted, you have to mark it @Transient
          • jpa assumes you want all fields persisted on pojo, unless they are marked
        • document how Boolean type persistence for Y/N is handled
      • Include documentation on how to use our new custom criteria api and how it differs from the OJB version
      • include documentation on how to write JPQL and translate from OJB criteria to JPQL (sort of a standard approach)
      • document any best practices that we recommend (i.e. JPQL over criteria, how to configure entity managers, etc.)
      • Document how to run the conversion script and exactly what it does
      • We should also be sure to include a step-by-step guide that someone follow to perform the conversion
      • include general instructions on how to write a DAO for JPA
      • document how to configure a Rice client application for JPA
        • in Spring, etc.
      • document the JPA feature that allows you to verify the jpa mappings vs. your database, this will probably mostly come in handy for development and verifications purposes

      This guide is a team wide task. It is expected for everyone working on the JPA conversion to add to this guide.

      The current guide location is:
      https://test.kuali.org/confluence/display/KULRICE/JPA+Conversion+Guide

      Here's a list of some of the JPA information we have so far compiled:

      Nate's guide (VERY good source on the conversion)
      https://test.kuali.org/confluence/display/KULRICE/JPA+Analysis

      KS JPA Guide (General info on using JPA):
      https://test.kuali.org/confluence/display/KULSTA/JPA

      https://test.kuali.org/confluence/display/KULRICE/Finish+JPA+Implementation+for+Rice+1.1

      https://test.kuali.org/confluence/display/KULRICE/Implementation+Details

      https://test.kuali.org/confluence/display/KULRICE/Rice+JPA+Issues

        Issue Links

          Activity

          Garey Taylor made changes -
          Field Original Value New Value
          Description - Just a general comment - this document needs to be written not only for a target audience that includes the KFS and KC projects, but also any existing Rice client applications that are out there in the wild
          - Include just a general overview of why we are making the change, what JPA is, information on the default implementation we are using
          - reference that we were hoping to use JPA 2.0 but it won't be available
          - document that we are dropping support for OJB so this is an impacting and forced upgrade
          - Have a quick introduction with some examples of how to map objects in JPA and what the different annotations are that we are likely to use
          -- also need to document any custom annotations and the vendor specific ones that we are using
          - Document the difference between OJB and JPA and how they need to be handled
          -- store and persist/merge difference
          -- if you don't want a field to be persisted, you have to mark it @Transient
          --- jpa assumes you want all fields persisted on pojo, unless they are marked
          -- document how Boolean type persistence for Y/N is handled
          - Include documentation on how to use our new custom criteria api and how it differs from the OJB version
          - include documentation on how to write JPQL and translate from OJB criteria to JPQL (sort of a standard approach)
          - document any best practices that we recommend (i.e. JPQL over criteria, how to configure entity managers, etc.)
          - Document how to run the conversion script and exactly what it does
          - We should also be sure to include a step-by-step guide that someone follow to perform the conversion
          - include general instructions on how to write a DAO for JPA
          - document how to configure a Rice client application for JPA
          -- in Spring, etc.
          - document the JPA feature that allows you to verify the jpa mappings vs. your database, this will probably mostly come in handy for development and verifications purposes


          This guide is a team wide task. It is expected for everyone working on the JPA conversion to add to this guide.

          The current guide location is:
          https://test.kuali.org/confluence/display/KULRICE/JPA+Conversion+Guide

          Here's a list of some of the JPA information we have so far compiled:
          - Just a general comment - this document needs to be written not only for a target audience that includes the KFS and KC projects, but also any existing Rice client applications that are out there in the wild
          - Include just a general overview of why we are making the change, what JPA is, information on the default implementation we are using
          - reference that we were hoping to use JPA 2.0 but it won't be available
          - document that we are dropping support for OJB so this is an impacting and forced upgrade
          - Have a quick introduction with some examples of how to map objects in JPA and what the different annotations are that we are likely to use
          -- also need to document any custom annotations and the vendor specific ones that we are using
          - Document the difference between OJB and JPA and how they need to be handled
          -- store and persist/merge difference
          -- if you don't want a field to be persisted, you have to mark it @Transient
          --- jpa assumes you want all fields persisted on pojo, unless they are marked
          -- document how Boolean type persistence for Y/N is handled
          - Include documentation on how to use our new custom criteria api and how it differs from the OJB version
          - include documentation on how to write JPQL and translate from OJB criteria to JPQL (sort of a standard approach)
          - document any best practices that we recommend (i.e. JPQL over criteria, how to configure entity managers, etc.)
          - Document how to run the conversion script and exactly what it does
          - We should also be sure to include a step-by-step guide that someone follow to perform the conversion
          - include general instructions on how to write a DAO for JPA
          - document how to configure a Rice client application for JPA
          -- in Spring, etc.
          - document the JPA feature that allows you to verify the jpa mappings vs. your database, this will probably mostly come in handy for development and verifications purposes


          This guide is a team wide task. It is expected for everyone working on the JPA conversion to add to this guide.

          The current guide location is:
          https://test.kuali.org/confluence/display/KULRICE/JPA+Conversion+Guide

          Here's a list of some of the JPA information we have so far compiled:
          https://test.kuali.org/confluence/display/KULRICE/Finish+JPA+Implementation+for+Rice+1.1

          https://test.kuali.org/confluence/display/KULRICE/Implementation+Details

          https://test.kuali.org/confluence/display/KULRICE/Rice+JPA+Issues


          Garey Taylor made changes -
          Description - Just a general comment - this document needs to be written not only for a target audience that includes the KFS and KC projects, but also any existing Rice client applications that are out there in the wild
          - Include just a general overview of why we are making the change, what JPA is, information on the default implementation we are using
          - reference that we were hoping to use JPA 2.0 but it won't be available
          - document that we are dropping support for OJB so this is an impacting and forced upgrade
          - Have a quick introduction with some examples of how to map objects in JPA and what the different annotations are that we are likely to use
          -- also need to document any custom annotations and the vendor specific ones that we are using
          - Document the difference between OJB and JPA and how they need to be handled
          -- store and persist/merge difference
          -- if you don't want a field to be persisted, you have to mark it @Transient
          --- jpa assumes you want all fields persisted on pojo, unless they are marked
          -- document how Boolean type persistence for Y/N is handled
          - Include documentation on how to use our new custom criteria api and how it differs from the OJB version
          - include documentation on how to write JPQL and translate from OJB criteria to JPQL (sort of a standard approach)
          - document any best practices that we recommend (i.e. JPQL over criteria, how to configure entity managers, etc.)
          - Document how to run the conversion script and exactly what it does
          - We should also be sure to include a step-by-step guide that someone follow to perform the conversion
          - include general instructions on how to write a DAO for JPA
          - document how to configure a Rice client application for JPA
          -- in Spring, etc.
          - document the JPA feature that allows you to verify the jpa mappings vs. your database, this will probably mostly come in handy for development and verifications purposes


          This guide is a team wide task. It is expected for everyone working on the JPA conversion to add to this guide.

          The current guide location is:
          https://test.kuali.org/confluence/display/KULRICE/JPA+Conversion+Guide

          Here's a list of some of the JPA information we have so far compiled:
          https://test.kuali.org/confluence/display/KULRICE/Finish+JPA+Implementation+for+Rice+1.1

          https://test.kuali.org/confluence/display/KULRICE/Implementation+Details

          https://test.kuali.org/confluence/display/KULRICE/Rice+JPA+Issues


          - Just a general comment - this document needs to be written not only for a target audience that includes the KFS and KC projects, but also any existing Rice client applications that are out there in the wild
          - Include just a general overview of why we are making the change, what JPA is, information on the default implementation we are using
          - reference that we were hoping to use JPA 2.0 but it won't be available
          - document that we are dropping support for OJB so this is an impacting and forced upgrade
          - Have a quick introduction with some examples of how to map objects in JPA and what the different annotations are that we are likely to use
          -- also need to document any custom annotations and the vendor specific ones that we are using
          - Document the difference between OJB and JPA and how they need to be handled
          -- store and persist/merge difference
          -- if you don't want a field to be persisted, you have to mark it @Transient
          --- jpa assumes you want all fields persisted on pojo, unless they are marked
          -- document how Boolean type persistence for Y/N is handled
          - Include documentation on how to use our new custom criteria api and how it differs from the OJB version
          - include documentation on how to write JPQL and translate from OJB criteria to JPQL (sort of a standard approach)
          - document any best practices that we recommend (i.e. JPQL over criteria, how to configure entity managers, etc.)
          - Document how to run the conversion script and exactly what it does
          - We should also be sure to include a step-by-step guide that someone follow to perform the conversion
          - include general instructions on how to write a DAO for JPA
          - document how to configure a Rice client application for JPA
          -- in Spring, etc.
          - document the JPA feature that allows you to verify the jpa mappings vs. your database, this will probably mostly come in handy for development and verifications purposes


          This guide is a team wide task. It is expected for everyone working on the JPA conversion to add to this guide.

          The current guide location is:
          https://test.kuali.org/confluence/display/KULRICE/JPA+Conversion+Guide

          Here's a list of some of the JPA information we have so far compiled:

          Nate's guide (VERY good source on the conversion)
          https://test.kuali.org/confluence/display/KULRICE/JPA+Analysis

          KS JPA Guide (General info on using JPA):
          https://test.kuali.org/confluence/display/KULSTA/JPA

          https://test.kuali.org/confluence/display/KULRICE/Finish+JPA+Implementation+for+Rice+1.1

          https://test.kuali.org/confluence/display/KULRICE/Implementation+Details

          https://test.kuali.org/confluence/display/KULRICE/Rice+JPA+Issues


          James Smith made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          James Smith made changes -
          Status In Progress [ 3 ] Open [ 1 ]
          Garey Taylor made changes -
          Assignee James Smith [ jksmith ] Garey Taylor [ gtaylor ]
          Garey Taylor made changes -
          Link This issue relies on KULRICE-3795 [ KULRICE-3795 ]
          Garey Taylor made changes -
          Assignee Garey Taylor [ gtaylor ]
          Jessica Coltrin (Inactive) made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Won't Fix [ 2 ]
          Jessica Coltrin (Inactive) made changes -
          Project Kuali Rice Documentation [ 10440 ] Kuali Rice Development [ 10220 ]
          Key KRDOC-147 KULRICE-6014
          Fix Version/s 2.0 [ 14190 ]
          Fix Version/s 2.0 [ 15611 ]
          Affects Version/s 2.0 [ 14190 ]
          Affects Version/s 2.0 [ 15611 ]
          Rice Lead jcoltrin
          Component/s Documentation [ 11241 ]
          Component/s Documentation [ 11241 ]
          Component/s Documentation [ 11241 ]
          Component/s Documentation [ 11241 ]
          Component/s Documentation [ 11241 ]
          Component/s Installation and Configuration [ 12690 ]
          Component/s Client Developer [ 12692 ]
          Component/s Technical [ 12694 ]
          Component/s General [ 12700 ]
          Component/s Developer [ 12790 ]
          Eric Westfall made changes -
          Fix Version/s 1.1-JPA [ 16454 ]
          Fix Version/s 2.0 [ 14190 ]
          Eric Westfall made changes -
          Start Date
          Fix Date [ set to sprint end date ]
          Jessica Coltrin (Inactive) made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Shem Patterson (Inactive) made changes -
          Workflow custom [ 78312 ] Copy of custom for rice [ 211600 ]
          Shem Patterson (Inactive) made changes -
          Workflow Copy of custom for rice [ 211600 ] custom [ 221348 ]
          Shem Patterson (Inactive) made changes -
          Workflow custom [ 221348 ] Rice Workflow [ 231096 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Garey Taylor
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel