Skip to content

Conversation

@goekay
Copy link
Member

@goekay goekay commented Oct 31, 2025

No description provided.

* use html code for line break in generated file in order for pom.xml not to look weird
* use "$schema" field as an anchor for replacement. this anchor is more general ("definitions" can be a miss for JSON schemas that do NOT use it, i.e. if the payload is empty).
the only caveat with this approach is, that "javaInterfaces" becomes the first field in the object in front of "$schema". but the order of fields in JSON objects should not matter anyways.
* prepare for multiple executions (for different OCPP versions, for a new dir to read JSON files from)
* add schema files from original source
* adjust maven plugins to generate POJOs properly
@goekay goekay linked an issue Oct 31, 2025 that may be closed by this pull request
@goekay
Copy link
Member Author

goekay commented Oct 31, 2025

FYI @juherr if you would like to take a look ;)

Copy link

@juherr juherr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍
Still, I’d secretly love to see a dedicated module per target and version baked right into Steve 😉

@goekay goekay merged commit d0124e1 into master Nov 1, 2025
1 check passed
@goekay goekay deleted the 18-add-ocpp-16-security-3rd-edition-schema branch November 1, 2025 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add OCPP 1.6 security 3rd edition schema

3 participants