Age | Commit message (Collapse) | Author | Files | Lines |
|
- Update zusemsg schema to version 2020-02-26
|
|
|
|
|
|
|
|
- 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.
|
|
|
|
|
|
|
|
|
|
|
|
- Handle InterruptedExceptions as discussed in
https://stackoverflow.com/questions/3976344/handling-interruptedexception-in-java
- Remove unused imports.
|
|
- Refactor: Move genTimestamp from ITMzsServiceTest to TestUtils
(because needed in multiple test cases).
- application.yaml: Complete app-client config in config profile.
|
|
|
|
- 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.
|
|
- Warning: Signatures of examples are not valid.
|
|
- 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.
|
|
|
|
- Update Changelog.
- Move Changelog to dedicated file.
- Restructure / reframe specification.
|
|
- 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.
|
|
- 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
|
|
- 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.
|
|
- 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.
|
|
|
|
|
|
- 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.
|
|
|
|
|
|
- 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.
|
|
|
|
|
|
|
|
|
|
- Reason: Consistency
|
|
- 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#
|
|
|
|
|
|
- Apparently, cgit has problems rendering XML files in the /about/
path. Therefore, I change links to the /tree/ path.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
- 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'
|
|
|
|
|
|
|
|
|