Part 1 showed how to get started with creating an addon, add relevant POM dependencies, build and install the addon using Forge shell, add a new command
batch-new-jobxml, and add
--writer parameters to the newly added command.
Part 2 showed how to identify classes for each CLI parameter that already honor the contract required by the Batch specification.
Part 3 showed how parameters can be made required, created templates for reader, processor, and writer, validated the specified parameters.
This part shows:
- Fixed the issues from part 3 and generates new JobXML when reader, processor, and writer are specified
- Added a new test to test the command
- How Forge can be used in debug mode to debug add ons
As always, the evolving source code is available at github.com/javaee-samples/forge-addons. The test code debugging will continue in the next episode.