Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Description
When creating reply descriptions, DefaultOperationDescriptionProvider calls attributeDescriptionResolver.getOperationParameterDescription instead of attributeDescriptionResolver.getOperationReplyValueTypeDescription.
A fix needs to not break compatibility for existing users of the incorrect behavior; i.e. call the correct method in a try block, catch any MissingResourceException, and if caught call the incorrect method.
Attachments
Issue Links
- is related to
-
WFLY-5754 Use specific description for reply value types in TimerAttributeDefinition and LegacySupport
- Pull Request Sent