Hello Clay, glad that you want to use and extend Fluent Job API for the new Git action :) Exactly the type of use case the API was born to serve.
Currently the Action, Converter, Builder, ... classes are all handwritten, only the JAXB ones (everything in org.apache.oozie.fluentjob.api.generated package) are generated. There is a guide *how to extend manually <https://github.com/apache/oozie/blob/master/docs/src/site/twiki/DG_FluentJobAPI.twiki#L352-L363>*, which is tedious and error prone. I can help you work on the Fluent Job API extension. If anyone comes up with a better idea, like using JavaCC or other tools to generate Action, Builder, and Converter classes, please feel free to discuss. Andras On Tue, Jul 31, 2018 at 2:42 AM Clay B. <[email protected]> wrote: > Hello, > > I realized I should write a few more tests for OOZIE-2877 (Oozie Git > Action) and figured it would be useful to use the new fluent API > (from OOZIE-2399) for the test. Then, I saw all the builders in > fluent-job/fluent-job-api/src/main/java/org/apache/oozie/fluentjob/api/action > > and the examples in > examples/src/main/java/org/apache/oozie/example/fluentjob/. > > I take it these are all hand-written or is there a generator one can point > me to which can read the XSD to create the necessary action and builder? > (I saw some generic *{Configuration,Launcher,Prepare}Converters in there > which look like I can simply copy and modify the class names... > > (An aside, what's the thought for external folks who are using custom > actions and who want to use the fluent API is there an extension point > for a custom bundled action?) > > -Clay >
