Middleware that allows a sender application to send delivery requests to delivery services https://git.egiz.gv.at/moa-zs/atom?h=master 2020-03-03T07:53:43+00:00 2020-03-03T07:53:43+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2020-03-03T07:53:11+00:00 urn:sha1:260200a55c07a9a5a8beab70dcf1980e522c438b 2020-02-18T13:05:18+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2020-02-18T13:04:27+00:00 urn:sha1:c257eea0453dfb484cf4f7a68ccc04a472d08bb7 2019-12-09T08:38:39+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-12-09T08:36:48+00:00 urn:sha1:5cb5e4803e315bb717c9db882f60c848da8e660c - Refactor: Move genTimestamp from ITMzsServiceTest to TestUtils (because needed in multiple test cases). - application.yaml: Complete app-client config in config profile. 2019-12-09T07:53:56+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-12-09T07:53:56+00:00 urn:sha1:a9585d867a2b432f6d75237e0857dd8af2daf554 2019-12-03T08:08:44+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-12-02T13:26:42+00:00 urn:sha1:8799a27e8d73c5e079d549f6d76abf861d75ee9e - Problem: I fixed CompletableFuture.*async within the DeliveryRequest flow, but forgot to do the same for the DeliveryRequestStatus / DeliveryNotification flow. - Solution: Ensure that all CompletableFuture.*async() invocations have Spring's task executor attached. 2019-11-29T14:56:44+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-11-29T14:56:44+00:00 urn:sha1:6dbe979e0b6bd6236db304b034ad592a4aeacabc - Refactor: Replace createSoap1{1,2} with create{Tnvz,App,Msg}Client. Configure each method with zusespec's specific parameters. Reason: Each service requires different parameters (e.g. with / without MTOM? soap11 / soap12? store responses in binary respository - yes/no?). These parameters could be placed in the client configuration of application.yaml. Since the parameters are tied to zusespecs, they do not need to be configurable via application.yaml. Another benefit for this refactoring is to improve readability. - Fix: Disable "Store Response" for TNVZ Client and App Client 2019-11-29T13:54:28+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-11-29T13:54:28+00:00 urn:sha1:a5b8668c0c7916a8fe2b84122d537a3e0bd67002 - Former: Fail with Exception. - Now: Issue a warning and fall back to default configuration profile after verifying that sinks in default configuration profile are correctly configured. - Refactor: Make DEFAULT_CONFIG_KEY static. 2019-11-22T13:05:10+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-11-22T12:57:41+00:00 urn:sha1:7acd8cf9b3bd0aacea61fff3a07e17b9b57ad8cc - 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. 2019-10-30T15:06:12+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-10-30T15:06:12+00:00 urn:sha1:c7551ed1dbf25fd786500a1516ddec9ec12dcf84 - Reason: Consistency 2019-10-04T09:20:20+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-10-04T09:17:48+00:00 urn:sha1:0727f68a2b899540fa951bfb22f9168bb1604b89