From 8f3b805a558c4ed454db2b691032cea800d7b6dd Mon Sep 17 00:00:00 2001 From: Christof Rabensteiner Date: Tue, 16 Jul 2019 14:33:26 +0200 Subject: Implement ForwardResponseToService Sink And All Its Implications 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. --- pom.xml | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'pom.xml') diff --git a/pom.xml b/pom.xml index 5ad5d11..6418481 100644 --- a/pom.xml +++ b/pom.xml @@ -188,6 +188,10 @@ ${project.basedir}/src/main/resources/mzs/app2mzs.wsdl classpath:mzs/app2mzs.wsdl + + ${project.basedir}/src/main/resources/mzs/mzs2app.wsdl + classpath:mzs/mzs2app.wsdl + ${project.basedir}/src/main/resources/zusemsg/app2zuse_p2.wsdl classpath:zusemsg/app2zuse_p2.wsdl -- cgit v1.2.3