-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
7.1.0.DR7
-
None
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.
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
JBEAP-7354 Document meaning of nillable attribute in management model
-
- Closed
-
