[MGNLWCS-77] Do not hardcode FormProcessorFailedException message Created: 11/Sep/14  Updated: 05/Dec/14  Resolved: 05/Dec/14

Status: Closed
Project: Websphere Commerce Integration
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.1, 1.1

Type: Bug Priority: Neutral
Reporter: Milan Divilek Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

info.magnolia.wcs.integration.form.PersonUpdateFormProcessor#personServiceCall
info.magnolia.wcs.integration.form.PersonRegistrationFormProcessor#personServiceCall
info.magnolia.wcs.integration.form.AddressBookFormProcessor#newAddressActionProcess
info.magnolia.wcs.integration.form.AddressBookFormProcessor#editAddressActionProcess
info.magnolia.wcs.integration.form.AddressBookFormProcessor#removeAddressActionProcess
...

All these methods have hardcoded error message if rest service call failed. Instead of hardcoded message we should use error message from rest service which contains reason why call failed.

e.getResponse().readEntity(ObjectNode.class).findValue("errorMessage").asText();

Generated at Mon Feb 12 11:13:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.