Middleware that allows a sender application to send delivery requests to delivery services https://git.egiz.gv.at/moa-zs/atom?h=2.0.0-RC1 2019-09-03T11:06:48+00:00 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 2019-07-18T07:23:00+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-07-18T07:23:00+00:00 urn:sha1:6d30f261c618a3b69a8f1be092056383e6dea424 - Service Timeout : Add service timeout to mzs schema (DeliveryRequest / Config), application.yaml, convert service timeout from spring environment to Config, and merge service timeouts in Configs. - Handling of Asynchronous DeliveryRequestStatus: Move "Applying Response Sinks" from backend into dedicated component "MsgResponseSinkHub" and integrate SinkHub into MzsService (apply sinks to asynchronous responses). - Remove line breaks in SignatureVerifier's log statements. - Revise documentation of parameters in application.yaml. 2019-07-16T14:53:41+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-07-16T14:53:41+00:00 urn:sha1:896195cc9b287a3f41008cc85997b9c2209120b8 Mzs Schema Changes: - Formerly: The mzs:DeliveryNotificationType is a choice between Success And Error; Change: Wrap choice in a sequence. Reason: msg 2.0.0 adds fields that fit best in this sequence. Adding new fields to Success or Error duplicates code, whereas adding it to the base type (which is MessageType) also affects mzs:DeliveryRequestStatus. - Add msg:SenderDetails, ReceiverDetails, user, AdditionalFormat, NotificationsPerformed; Reason: It was added to zusemsg 2.0.0. 2019-07-16T12:33:26+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-07-16T12:33:26+00:00 urn:sha1:8f3b805a558c4ed454db2b691032cea800d7b6dd MZS Schema Change: - Add configuration for ForwardResponseToServiceSink (add parameters in mzs:DeliveryRequest/Config) - Add sink configuration in application.yaml, convert from Spring Environment to ConfigType, and merge ConfigTypes. - Validate sink configuration completeness. Contract added: - Add contract mzs2app.wsdl: This contract specifies how mzs:DeliveryRequestStatus' and mzs:DeliveryNotifications are forwarded to the sender application. - Implement "ForwardResponseToService" Sink. - Add and implement MsgResponse.sendToMzsClient() : This is a somewhat unfortunate solution because, intuitively, sending should be done by it's caller, the "ForwardResponseToService"-sink. However, this solution prevents differences between msg:DeliveryRequestStatus and msg:DeliveryNotification (and code that needs to handle differences, i.e. sending) from sprawling outside of the respective MsgResponse derivatives. We move the entire "send" process into MsgResponse to prevent a hard-to-maintain "if type == notification then do x else to y" construct in ForwardResponseToServiceSink. Otherwise, introducing the MsgResponse wrapper was pointless. 2019-07-15T10:09:28+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-07-15T10:04:26+00:00 urn:sha1:d9e5864f48d261c06de1f1d34000ff6156155569 - Fix in ConfigUtil: SaveResponseToFile boolean would override LogResponse configuration (Copy Paste Error). 2019-07-12T13:40:05+00:00 Christof Rabensteiner christof.rabensteiner@iaik.tugraz.at 2019-07-12T13:40:05+00:00 urn:sha1:25d68c8900c2cc791f03ea3db173955ca237fd55 - MZS Schema Change: Add "MsgResponseSinks" element to mzs:DeliveryRequest/Config that allows sender to configure how MsgResponses should be archived. - ConfigUtil: Interpret MsgResponseSink parameters from Spring Environment and merge with ConfigType. - MsgResponseBackend: Send responses to sinks according to MsgResponseSinks in Config - application.yaml: Add MsgResponseSinks parameter to configuration. - Uncouple Sink implementations from java.util.function.Function, because the sink interfaces are going to differ and there is no need to unite them under one interface. - Add and test LogResponseSink, which logs responses to it's logger. - MsgResponse: Add JAXB getter for response. Reason: Can be passed to marshaller.