NIFI-16021 Improved JoltTransformJSON error message when specified JOLT spec is invalid and ensured leading single and multi-line Java comments are supported when the Jolt spec is specified as text.

[dan-s1]

Summary

NIFI-16021

Also added tests to ensure ValidateJson causes Json parsing exception when any Java comments is specified before or inside a schema.

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

• Apache NiFi Jira issue created

Pull Request Tracking

• Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
• Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000
• Pull request contains commits signed with a registered key indicating Verified status

Pull Request Formatting

• Pull Request based on current revision of the main branch
• Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

• Build completed using ./mvnw clean install -P contrib-check
  • JDK 21
  • JDK 25

Licensing

• New dependencies are compatible with the Apache License 2.0 according to the License Policy
• New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

• Documentation formatting appears as expected in rendered files

[exceptionfactory]

Thanks @dan-s1. Although changing the message itself is one approach, it seems better to handle the formatting in the custom validation method. This would align with the general practice of avoiding including exception cause messages. It would also avoid changing runtime behavior for the sake of the validation method.

[dan-s1]

@exceptionfactory Please let me know if the latest change is what you had in mind. Thanks!

[exceptionfactory]

Thanks @dan-s1, the revised approach looks closer to what I had in mind. I recommendation a small adjustment.