Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8891 Certify EAP 5.1 with Java 7
  3. JBPAPP-9316

Deprecate usage of PropertyEditorManager

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: EAP_EWP 5.2.0
    • Component/s: None
    • Labels:
    • Affects:
      Release Notes
    • Estimated Difficulty:
      High
    • Release Notes Text:
      Hide
      Oracle's JDK7 changed the way in which the <literal>ProperyEditors</literal> registry was stored. What was previously a global registry became a per <literal>ThreadGroup</literal> registry. EAP 5.2.0 has removed the use of <literal>PropertyEditorManager</literal> and implementing a new facility provided by <literal>jboss-common-beans</literal> to accommodate this. Clients whose applications use custom <literal>ProperyEditors</literal> should be aware of this change.
      Show
      Oracle's JDK7 changed the way in which the <literal>ProperyEditors</literal> registry was stored. What was previously a global registry became a per <literal>ThreadGroup</literal> registry. EAP 5.2.0 has removed the use of <literal>PropertyEditorManager</literal> and implementing a new facility provided by <literal>jboss-common-beans</literal> to accommodate this. Clients whose applications use custom <literal>ProperyEditors</literal> should be aware of this change.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      In JDK 7 the storing of the registry of PropertyEditors has been changed from a global registry to a per ThreadGroup registry. The effect is that previously the custom PEs could always be located, now the PEs can only be located when looked up from the correct ThreadGroup.

      Removing the usage of PropertyEditorManager and using the facility provided by jboss-common-beans will fix this problem.

        Gliffy Diagrams

          Attachments

          1. eap5-jdk7-common-beans.patch
            80 kB
          2. eap5-jdk7-common-beans.patch
            80 kB
          3. eap5-jdk7-common-beans-v3.patch
            80 kB
          4. eap5-jdk7-common-beans-v4.patch
            99 kB
          5. eap5-jdk7-common-beans-v5.patch
            103 kB
          6. eap5-jdk7-common-beans-v5.patch
            108 kB
          7. eap5-jdk7-common-beans-v6.patch
            131 kB
          8. eap5-jdk7-common-beans-v6.patch
            147 kB
          9. eap5-jdk7-common-beans-v6.patch
            135 kB
          10. settings_bck.xml
            13 kB
          11. test.patch
            135 kB
          12. testsuite-build-xml.patch
            1 kB

            Issue Links

            is related to

            Bug - A problem which impairs or prevents the functions of the product. WFLY-833 Wrong PropertyEditor is used by ThreadGroups other than "ModelController ThreadGroup" in JDK 7

            • Major - A request that should be considered seriously but is not a show stopper.
            • Open

            Bug - A problem which impairs or prevents the functions of the product. JBPAPP-10561 jboss-common-beans is not listed in jbossall-client

            • Critical - An upcoming version that is affected by this issue cannot be released until it's addressed. A critical bug is one that crashes the application, causes loss of data or severe memory leak.
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. JBPAPP-10578 RPM: jboss-common-beans is not listed in jbossall-client

            • Critical - An upcoming version that is affected by this issue cannot be released until it's addressed. A critical bug is one that crashes the application, causes loss of data or severe memory leak.
            • Closed

            Task - A task that needs to be done. JBPAPP-9462 Upgrade to JBoss Commons Beans 1.0.1

            • Major - A request that should be considered seriously but is not a show stopper.
            • Closed

              Activity

                People

                • Assignee:
                  baranowb Bartosz Baranowski
                  Reporter:
                  wolfc Carlo de Wolf
                  Writer:
                  Scott Thomas
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 3 days Original Estimate - 3 days
                    3d
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 2 weeks, 1 minute
                    2w 1m