NIFI-6532 Added documentation to TransformXML to explain the usage of dynamic properties in stylesheets.

[dan-s1]

Summary

NIFI-6532
This PR is adds documentation to detail the use of dynamic properties in XSLT style sheets.

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]

@dan-s1 This looks like some helpful improvements and corrections, but the test failures on Windows are concerning, and appear to point to some issues with the new methods. It may be best to decouple documentation additions from tests changes for clarity of review.

[dan-s1]

@exceptionfactory Its not exactly clear to me what the errors are on the Windows box. The last thing I saw was about a directory not existing which did not relate to my additions.

[exceptionfactory]

@exceptionfactory Its not exactly clear to me what the errors are on the Windows box. The last thing I saw was about a directory not existing which did not relate to my additions.

Thanks, sounds like it could have been an intermittent issue then.

[exceptionfactory]

I recommend decoupling the CapturingLogger change to a separate Jira issue. Adding the new unit tests for TransformXml looks good, but since CapturingLogger is a key part of nifi-mock, it seems a bit too buried given the summary context of this issue focusing on documentation.

[dan-s1]

I understand that, but the fix won't be as apparent since there are no unit tests for CapturingLogger. It is in this ticket, a concrete instance where the issue crops up as I could not check for ValidationException without the stack trace. Should I perhaps separate the unit tests also and include those as well as the fix for CapturingLogger and keep this PR for the documentation only?

[exceptionfactory]

Should I perhaps separate the unit tests also and include those as well as the fix for CapturingLogger and keep this PR for the documentation only?

Yes, that would work. Since the Jira issue, and PR title, focus on documentation, decoupling the testing would be helpful for tracking purposes.

[dan-s1]

Okay I have reduced this PR to only the addition of the additionalDetails.md file and I have created NIFI-15715 to handle the other changes and submitted PR #11008.

[exceptionfactory]

Thanks for refocusing this PR @dan-s1, looks good! +1 merging