mbeckerle opened a new pull request #651:
URL: https://github.com/apache/daffodil/pull/651
I am looking for initial validation of these changes, whether this is
isolating layer definitions sufficiently from Daffodil internals, etc.
Nothing is dynamically loading anything yet. I'm first refactoring things to
hide Daffodil internals from the layer implementations.
The thought is, once this is properly refactored, the dynamic loading aspect
will be far easier.
There are two commits here. The first is most of it. I didn't squash the
second one because it is just a fix for 2 tests that were failing. But as these
changes should NOT have changed functionality, I don't understand why these
fixes (to test data) were needed.
Changes included:
Moved AISPayloadArmoring into daffodil-test.
Left the other "built-in" layer transformers in daffodil-runtime1 for
now.
Layers now are defined with a layer-compiler that does
schema-compile-time
checking.
Layers are defined using only LayerInfo, LayerRuntimeInfo (the
serialized one), and LayerCompileInfo all of which hide daffodil's
internals, but expose the layer properties for use by the layer
developer.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
