moa-zs/src/main, branch 2.0.0-RC5

Fix Msg Schema Error: Honor Mutual Exclusiveness of

2019-11-22T13:05:10+00:00

- Problem: When activating the QueryPersonRequest, the TNVZ returns an Identification element that needs to be integrated into the msg:DeliveryRequest as a child of Receiver. The Identification child is mutually exclusive to another sequence consisting of (Person, AustrianAddressesOnly, Address). I forget to delete the sequence when adding the Identifcation element and violate the the msg schema. - Solution: Delete sequence when adding Identification. - Test the fix in test case. Thanks to Johannes Hörtnagl for pointing out the problem.

Fix Error in TNVZ QueryPerson Request

2019-11-07T07:06:38+00:00

- Problem: When assembling the TNVZ Query Person Request, I convert the Sender with msgp's ObjectFactory.createPerson. The marshaller will then create a Corporate body like this: What we really want is this: - Solution: Replace createPerson with createCorporateBody. - Thanks to Johannes Hörtnagl and Christoph Kaiser-Feistmantl for the feedback.

Remove Unused TNVZ Version

2019-11-06T12:04:11+00:00

Bump zusetnvz Contracts to Version 2.2.008

2019-11-06T11:55:22+00:00

Refactor: Rename ClientFactory.create Interface

2019-10-30T15:06:12+00:00

- Reason: Consistency

Remove JAXB Class Not Found Fix

2019-10-30T15:04:03+00:00

- Problem: Apparently I used the wrong executor when supplying the backend tasks via CompletableFuture.supplyAsync(). This method relies on ForkJoinPool.commonPool(), and threads in this pool are not configured correctly? - Solution: Use spring-boots auto-configured TaskExecutor. - More Information on this issue can be found here: https://issues.apache.org/jira/browse/CXF-8100#

Fixes in app2mzs Schema and Code

2019-10-07T11:52:43+00:00

app2mzs Schema Changes: - mzs:MessageType/ZSDeliveryID was mandatory. However, in certain cases the ZSDeliveryID does not exist (Example: perform QueryPersonRequest, request fails > no ZSDeliveryID). This element is now optional. - mzs:Error/Code was of type xs:integer, is now xs:string. Reason: msg:Code is also of type string. Incorporate app2mzs schema changes into code base.

Resolve Sonarqube Findings

2019-10-07T07:37:38+00:00

Add Validation for TNVZ QueryPersonRequest

2019-10-04T12:32:41+00:00

Fix Validation Error Message

2019-10-04T11:06:26+00:00

- Error was assigned to TNVZ Client, but appeared in MSG Client.