Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-6949

Attribute default-extended-persistence-inheritance incorrectly set as nillable

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Minor
    • None
    • 7.1.0.DR7
    • JPA/Hibernate, User Experience
    • None

    Description

      The resource description of jpa subsystem says that default-extended-persistence-inheritance is nillable:

                  "default-extended-persistence-inheritance" => {
                "type" => STRING,
                "description" => "Controls how JPA extended persistence context (XPC) inheritance is performed. 'DEEP' shares the extended persistence context at top bean level.  'SHALLOW' the extended persistece context is only shared with the parent bean (never with sibling beans).",
                "expressions-allowed" => true,
                "nillable" => true,
                "default" => "DEEP",
                "allowed" => [
                    "DEEP",
                    "SHALLOW"
                ],
                "access-type" => "read-write",
                "storage" => "configuration",
                "restart-required" => "all-services"
            }

      However, only DEEP and SHALLOW are allowed values, which means the attribute cannot be null. When trying to undefine the attribute using 

       /subsystem=jpa:undefine-attribute(name=default-extended-persistence-inheritance)

      operation, the default value DEEP is set.

      The above observation can lead to confusion. In case the attribute cannot be null, nillable should be set to false.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-7021 IO worker attributes incorrectly marked as nillable

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-7022 Most of deployment scanner attributes are incorrectly marked nillable

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-7354 Document meaning of nillable attribute in management model

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              smarlow1@redhat.com Scott Marlow
              nziakova@redhat.com Nikoleta Ziakova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: