Fix event marshaller binding for input event streams. #1927
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is another case of SDK code generation failing when the event's structure name and the structure member name are not identical.
Description
This is similar to #1821 which fixed the problem for output event streams.
Motivation and Context
This fixes generation for services that do not align their structure member names and structure type names when modelling event streams.
Testing
I modified the existing unit tests. The previously generated client appears to be nonfunctional, as it references an
InputEventOne
class and anInputEventOneMarshaller
class, but the C2JModel only contains shapesInputEvent
andInputEventTwo
.I also tested this offline on a model that broke generation without this change.
Types of changes
Checklist
mvn install
succeedsLicense