-
Task
-
Resolution: Unresolved
-
Major
-
None
-
23.0.0.Beta1
-
None
-
Undefined
-
---
-
---
Please can you review your components integration with WildFly looking for issues with how the subsystem parses it’s configuration.
In particular we are looking for:
Cases where your component exposes an attribute that allows property expansion and the value is not resolved as an expression before using it in runtime services but the raw value is used instead
i.e. in an operation handler that executes in OperationContext.Stage.RUNTIME. Often this execution is in a method that overrides AbstractAddStepHandler.performRuntime or AbstractBoottimeAddStepHandler.performBoottime
Cases where attributes are defined as one type and handled as another
Cases where xml marshalling code is improperly using the attribute
E.g. by resolving the expression (it should not)
E.g. by directly reading the raw value and making logical decisions based on it (if (x.asBoolean()) writeThis else writeThat)
Cases where attributes are not covered by automatized test
- incorporates
-
WFLY-14539 Review for expansion expression testing in mod_cluster subsystem
- Closed
-
WFLY-14544 Review for expansion expression testing in singleton subsystem
- Closed
-
WFLY-14547 Review for expansion expression testing in jgroups subsystem
- Closed
-
WFLY-14548 Review for expansion expression testing in infinispan subsystem
- Coding In Progress
- is related to
-
WFLY-14545 The singleton subsystem socket-binding-preferences cannot support expressions
- Closed
-
WFLY-14551 EJB subsystem should not allow expressions for cache-container/bean-cache in passivation-store resource
- Closed
-
WFLY-14552 EJB subsystem should not allow expressions for client-mappings-clustering-name in remote resource
- Closed
-
WFLY-14581 JGroups subsystem does not persist client-socket-binding of the transport
- Closed
- relates to
-
WFLY-14511 Add EAP 7.3.0 transformers tests for clustering subsystems
- Closed