aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2020-02-18Update ChangelogChristof Rabensteiner1-0/+13
2020-02-18Timeout & Assync FixesChristof Rabensteiner2-5/+55
- Fix: Parser Error that occurs when MOA ZS goes into service timeout. - Fix: Improve exception handling on MOA ZS Async. - Before: When MOA ZS processes delivery request but hits a timeout, MOA ZS would answer syncronously to the Sender app and forward the result assynchronously at a later point. If an exception were to occur after the timeout, MOA ZS would swallow this exception. - Now: If an exception occurs, MOA ZS converts the exception into a response and hands it over to the sink hub for proper processing of the event.
2020-02-18SSL Tests: Fix RoutesChristof Rabensteiner1-5/+5
2020-02-18Bump to Version 2.0.0-RC8-SNAPSHOTChristof Rabensteiner1-1/+1
2020-01-20Docs: Fix Spelling of Property KeysChristof Rabensteiner1-2/+2
2020-01-07Add "large attachment" Example to curl FolderChristof Rabensteiner4-0/+87
2019-12-09Bump to Version 2.0.0-RC72.0.0-RC7Christof Rabensteiner2-1/+8
2019-12-09Refactor & FixesChristof Rabensteiner4-20/+27
- Handle InterruptedExceptions as discussed in https://stackoverflow.com/questions/3976344/handling-interruptedexception-in-java - Remove unused imports.
2019-12-09Add "Forward-Response-to-Service" Test CasesChristof Rabensteiner6-26/+148
- Refactor: Move genTimestamp from ITMzsServiceTest to TestUtils (because needed in multiple test cases). - application.yaml: Complete app-client config in config profile.
2019-12-09Test Refactor: Move SOAP Client Utilities into Dedicated ClassChristof Rabensteiner2-56/+66
2019-12-06Change msg service: Acknowledge Response iff Backend SucceedsChristof Rabensteiner4-30/+65
- Before: Upon receipt of a message via the msg/ endpoint, MOA ZS would immediately acknowledge the receipt without verifying that the message was successfully processed by the backend. - Now: MOA ZS receives a message via the msg/ endpoint, forwards it to the sinks, and acknowledges the receipt if and only if the processing succeeded.
2019-12-05Add Two Curl Examples to send msg:DeliveryNotifications to MOAZSChristof Rabensteiner4-0/+199
- Warning: Signatures of examples are not valid.
2019-12-05Fix Missing Parameters in ERVDeliveryConfirmed NotificationChristof Rabensteiner2-3/+30
- 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-12-05Bump to Version 2.0.0-RC7-SNAPSHOTChristof Rabensteiner1-1/+1
2019-12-03Bump to Version 2.0.0-RC62.0.0-RC6Christof Rabensteiner4-154/+173
- Update Changelog. - Move Changelog to dedicated file. - Restructure / reframe specification.
2019-12-03Finalize "Removal of JAXB Class Not Found Fix"Christof Rabensteiner6-16/+31
- 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-29Refactor & Fix Client Creation in Client FactoryChristof Rabensteiner6-31/+32
- 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-29Alter Case Handling "Get Notification where AppDeliveryID is unknown"Christof Rabensteiner4-33/+52
- 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-29Fix NPE When Receiver Is Identified by IdentityChristof Rabensteiner1-4/+14
- Problem: MOA ZS converts the mzs:Receiver/Person to msg:Receiver/Person even if mzs:Receiver/Person is null. - Solution: Distinguish Cases. - Add ClearingProfilID in mzs2msg conversion.
2019-11-28Bump to Version 2.0.0-RC6-SNAPSHOTChristof Rabensteiner1-1/+1
2019-11-22Bump to Version 2.0.0-RC52.0.0-RC5Christof Rabensteiner2-1/+5
2019-11-22Fix Msg Schema Error: Honor Mutual Exclusiveness of <Choice>Christof Rabensteiner2-3/+41
- 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-11-22Bump to Version 2.0.0-RC5-SNAPSHOTChristof Rabensteiner1-1/+1
2019-11-07Bump to Version 2.0.0-RC42.0.0-RC4Christof Rabensteiner2-1/+5
2019-11-07Fix Error in TNVZ QueryPerson RequestChristof Rabensteiner1-1/+1
- 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: <ns2:Person xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ns2:CorporateBodyType"> What we really want is this: <ns2:CorporateBody> - Solution: Replace createPerson with createCorporateBody. - Thanks to Johannes Hörtnagl and Christoph Kaiser-Feistmantl for the feedback.
2019-11-06Update Changelog2.0.0-RC3Christof Rabensteiner1-0/+5
2019-11-06Remove Unused TNVZ VersionChristof Rabensteiner1-1/+0
2019-11-06Bump to Version 2.0.0-RC3Christof Rabensteiner1-1/+1
2019-11-06Bump zusetnvz Contracts to Version 2.2.008Christof Rabensteiner2-6/+4
2019-10-30Refactor: Rename ClientFactory.create InterfaceChristof Rabensteiner6-14/+14
- Reason: Consistency
2019-10-30Remove JAXB Class Not Found FixChristof Rabensteiner4-96/+11
- 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#
2019-10-30Bump to v2.0.0-RC3-SNAPSHOTChristof Rabensteiner1-1/+1
2019-10-25Spec: Update Namespace ReferencesChristof Rabensteiner1-7/+7
2019-10-25Fix links to XML filesChristof Rabensteiner1-9/+9
- Apparently, cgit has problems rendering XML files in the /about/ path. Therefore, I change links to the /tree/ path.
2019-10-25Spec: Update Architecture Image ReferenceChristof Rabensteiner1-1/+1
2019-10-25Spec: Add & Describe MOA ZS ArchitectureChristof Rabensteiner3-1/+490
2019-10-25Spec: Remove TODO ItemChristof Rabensteiner1-3/+1
2019-10-07Fixup in Spec2.0.0-RC2Christof Rabensteiner1-1/+0
2019-10-07Bump to Version 2.0.0-RC2Christof Rabensteiner1-1/+1
2019-10-07Add tnvz-q Example to curl FolderChristof Rabensteiner6-2/+73
2019-10-07Update ChangelogChristof Rabensteiner1-0/+4
2019-10-07Fixes in app2mzs Schema and CodeChristof Rabensteiner2-5/+7
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-07Add Empty Ruleset for JacocoChristof Rabensteiner1-0/+4
- Fixes "Failed to execute goal org.jacoco:jacoco-maven-plugin:0.8.3:check (default-check) on project moa-zs: The parameters 'rules' for goal org.jacoco:jacoco-maven-plugin:0.8.3:check are missing or invalid" -error when running 'mvn verify'
2019-10-07Resolve Sonarqube FindingsChristof Rabensteiner6-10/+4
2019-10-07Reformat CURL ExampleChristof Rabensteiner1-12/+12
2019-10-07Update Changelog for 2.0.0-RC2Christof Rabensteiner2-1/+59
2019-10-04Add Validation for TNVZ QueryPersonRequestChristof Rabensteiner1-0/+6
2019-10-04Update readme.mdChristof Rabensteiner3-31/+33
- Put SSL client auth guide into separate file. - Add download link to apps.egiz.gv.at/releases. - Put note that cluster mode is not ready.
2019-10-04Fix Validation Error MessageChristof Rabensteiner1-1/+1
- Error was assigned to TNVZ Client, but appeared in MSG Client.
2019-10-04Fix Property Key "filetype" (Was "type") in application.yamlChristof Rabensteiner2-3/+3
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 01:05:13 +0000