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:50:12+00:00 urn:sha1:3e0238d96cb58459b5a67d2d113ba5469a3a8978 - Update zusemsg schema to version 2020-02-26 2019-12-05T08:16:36+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-12-05T08:16:36+00:00 urn:sha1:cf90865ce21f246a0358fd291324f511c5ed6e90 - mzs Schema Change: Introduce new type mzs:ERVConfirmedDelivery (which is a mzs:MessageType extension) and replace mzs:DeliveryNotification/msg:ERVConfirmedDelivery with mzs:ERVConfirmedDelivery. Reason: Necessary to provide all parameters to sender application (AppDeliveryID, DeliverySystem, ZSDeliveryID, a.o.). - Adapt Msg2MzsConverter accordingly. 2019-11-06T11:55:22+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-11-06T11:38:11+00:00 urn:sha1:29fa1643fa32a88f3e24c6aa3f1ab9dad945ab55 2019-10-07T11:52:43+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-10-07T11:52:43+00:00 urn:sha1:ee244162599b676d17d1974101ded38f74ea2898 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. 2019-10-03T14:09:47+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-10-03T14:09:47+00:00 urn:sha1:ee8c694c12850b27144a664c948c3b84398ead6f Upgrade zusemsg 2.2.0 to 2.2.007: - msg:RelayedViaERV - Change from boolean to complex type (ervcode). - Move from msg:DeliveryRequestStatusType/Success into msg:DeliveryRequestStatusType, which affects Success, Error, and PartialSuccess. - Was removed from DeliveryNotificationType. - Change msg:DeliveryNotification/Answer from list to singleton. - Change msg:DeliveryRequestStatusType/PartialSuccess is to type AnswerType. - msg:DeliveryRequestStatusType and msg:DeliveryNotificationType receive the attribute ID (for signature referencing). - Add new optional element msg:AustrianAdressesOnly (IndicatorType) to DeliveryRequestType/Receiver/(choice sequence). - Add new optional element ClearingProfilID to DeliveryRequestType/Sender. - Add new element ERVConfirmedDelivery, which subsitutes msg:Answer and extends msg:AbstractOperation - Has element ErvCode (also new token256 type). - Has element ERVDeliveryTimestamp. - Add new optional element TargetIdentification of type p:IdentificationType to msg:DeliveryNotification/User/ as optional element. - Add new enumeration "System" to msg:DeliveryNotification/User/Role. - Rename type AustrianLanguageType from "AustrianEthicMinorityLanguageType" to "AustrianLanguageType" and add "DE" as value. - msg:Tags were unbounded, now they are limited to 20. - VersionNumberType: Patch version can have three digits. Upgrade zusetnvz 2.2.0 to 2.2.006: - Add StandardMimeTypeList to tnvz:QueryPersonResponse and tnvz:QueryAdressabilityResponse. - Add AllStandardMimeTypes (indicator) to tnvz:PersonResult/Success. - Add optional msg:MetadataList to tnvz:PersonQueryType/Metadata tnvz:AddressabilityQueryType/Metadata. - Move tnvz:AustrianAdressesOnly to msg namespace. Carry zusemsg changes into app2mzs interface: - Switch namespace of AustrianAdressesOnly from tnvz to msg. - Add new optional element ClearingProfilID to mzs:DeliveryRequestType/Sender; Reason: Element was added to zusemsg 2.2.007. - Add new choice in mzs:DeliveryNotification to forward new answer type msg:ERVConfirmedDelivery to the app. - Move msg:RelayedViaERV from SuccessType into MessageType (now it's available to all types that derive from MessageType). Accommodate zusemsg/tnvz changes in code base: - TNVZHelper: Consider StandardMimeTypeList when assessing if DeliveryRequest/mimetypes overlap with TNVZ's Accepted Mimetypes. - Msg2MzsConverter: - Put getRelayedViaERV() into all DeliveryStatusRequest replies. - Honor that Notification/Answer is Singleton instead of List. - Handle case were DeliveryNotification/Answer is of type ERVConfirmedDeliveryType. - Remove RelayedViaERV from DeliveryNotification as this element is not available anymore. - NotificationResponse: Honor that Notification/Answer is Singleton instead of List. Fix all testcases and sample soap messages to comply with schema changes. 2019-09-03T11:06:48+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-09-03T11:06:48+00:00 urn:sha1:3b114adee71e1e2477898d55c91cd573f0e48857 ...since it's a client that communicates with the app. 2019-08-23T12:57:28+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-08-21T13:27:46+00:00 urn:sha1:763724b04d25d07fce5559c1d7a6c12badab937c - Reason: Integration tests need configuration, but config files should not be packaged into the final artifact. - Update paths. 2019-08-20T09:13:28+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-08-20T09:13:28+00:00 urn:sha1:2b8a7df25878f546ace25373f44baeb026cf6d2b - Change app2mzs schema: Add Custom Headers to ClientType Element. - Set custom headers in ClientFactory. - Parse custom headers from spring environment. - Merge custom headers from two different profiles. - Add example to application.yaml. - Test conversion of custom headers from spring profile - Test merging and overriding custom headers. 2019-07-22T11:02:19+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-07-22T11:02:19+00:00 urn:sha1:cb9a76eaafd37f921006822bcfe043655288bc63 Schema Changes: - Remove mzs:DeliveryRequest/TnvzMetaData because all metadata fields can be collected from DeliveryRequest and redundancy is not needed. Fixes and Refactoring in preprocess: - MzsDeliveryRequestValidator: Instead of returning false, throw an exception when a condition is not met, and explain which condition is not met / why it is not met in the exception's message. - Integrate interface change in ConfigProfileGenerator and DeliveryRequestAugmenter. - Rewrite and simplify DeliveryRequestAugmenter's augmentation. - ConfigUtil Fixes: Ensure that we do not override the wrong parameters while merging. This error appeared in tnvz / msg client, connection / receive timeout, key / trust store, and lax hostname verification / trust all. Fix Bugs in Interceptor / SoapUtils: - Problem: DOM access and information extraction was implemented somewhat sloppy. - SolutioN: Change DOM access interface to access DOM more efficiently. Add boundary checks and handle edge cases while extracting information from SOAP Messages. - Test those changes properly. Testing: - Implement Delivery Request Flow in ITEndToEndTest. - Start application on random port instead of fixed port when running integration tests. - Add assertions to tests in ITMzsServiceTest suite. Others Bug Fixes: - ServicesConfig: Ensure that mzs service and msg service run on different endpoint addresses (/msg and /mzs). - DeliveryRequestBackend: Throw exception when binary message is missing. Don't wrap the exception. - SaveResponseToFileSink: Wrap Response in JAXB Element (otherwise, marshaller does not recognize it) 2019-07-18T08:37:45+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-07-18T08:37:45+00:00 urn:sha1:d873625c0ced62e712dc1b1a7570b63482fd0a0a