diff options
author | Christof Rabensteiner <christof.rabensteiner@iaik.tugraz.at> | 2019-04-08 10:31:59 +0200 |
---|---|---|
committer | Christof Rabensteiner <christof.rabensteiner@iaik.tugraz.at> | 2019-04-08 10:31:59 +0200 |
commit | a8bd62ade64937e554e977c755e2989a798161cc (patch) | |
tree | 863b4ecaf0dcb11c081aaf0b6827b49bc9220d09 /src/main/java/at | |
parent | 648632858c007b361476953d0b3019c410a75fb7 (diff) | |
download | moa-zs-a8bd62ade64937e554e977c755e2989a798161cc.tar.gz moa-zs-a8bd62ade64937e554e977c755e2989a798161cc.tar.bz2 moa-zs-a8bd62ade64937e554e977c755e2989a798161cc.zip |
Update mzs:DeliveryRequest Schema
- Remove MZSDreq/Sender/ConfirmationAddress (because its already
Available in Sender/{WebserviceURL,EmailAddress})
- Simplify MZSDReq/Receiver (no actual schema change, just
refactoring)
- Remove XML Payload (because this delivery method does not exist in
zusemsg)
- Simplify Payload Schema and adapt it to zusemsg:Attachment
- Remove DayOfBirthType (because dead code)
- Metadata: replace mzs definition of metadata with reference to
msg:Metadata. Reason: Both interfaces work the exact same way so
there is no reason in not reusing the interface. Using the same
interface definitions does not affect the integration effort for app
developers, because the msg:metadata changed quite drastically and
app developers will need to integrate these changes anyways. The
changes in zusemsg:Metadata are so invasive that MOAZS cannot
prevent them from propagating into the app2mzs interfaces. A benefit
from reusing the msg:MetaData interface is that there will be less
types, less duplicate code, less repetition, and
therefore cleaner and easier to maintain.
Diffstat (limited to 'src/main/java/at')
0 files changed, 0 insertions, 0 deletions