org.hl7.fhir.core/org.hl7.fhir.core.generator
Grahame Grieve ed6b5f00c8 Add .toString for OperationOutcome.issue 2022-10-04 14:04:33 +11:00
..
configuration Add .toString for OperationOutcome.issue 2022-10-04 14:04:33 +11:00
src/org/hl7/fhir/core/generator new R5 release coming 2022-09-06 20:28:04 +10:00
.classpath Regenerate R4B code 2022-04-22 11:56:24 +10:00
.project add generator project files 2022-04-22 08:13:28 +10:00
readme.md Ensure that CVX uses tx.fhir.org, not UTG definitions which are wrong + Fix problems with Bundle validation for ids in collections and add additional search related validation + Remove check on ElementDefinition.id for R2B 2021-04-22 13:27:32 +10:00

readme.md

The Java Core Code Generator

Note: This code only generates the R5 java code. Older generated models are now maintained by hand.

To run this code, run the class JavaCoreGenerator with 3 parameters:

  • 1: fhir version to generate from (e.g. 4.1.0 or 'current'
  • 2: project directory to read configuration and templates from - e.g. C:\work\org.hl7.fhir\org.hl7.fhir.core\org.hl7.fhir.core.generator\configuration
  • 3: project directory to generate code into - e.g. C:\work\org.hl7.fhir\org.hl7.fhir.core\org.hl7.fhir.r5.new

The generation process depends on the code it generates - do not regenerate the master R5 code until you have tested that it generates correctly.

To test the generation:

  • create a new project, copy the existing R5 code into it, and get it compiling
  • make sure that project is not in the build path for the generator itself, which depends on the production R5 code
  • run the generation
  • refresh etc and make sure that the compiler is happy
  • copy the JUnit tests RoundTripTests into the copy project, update the constants, and execute it
  • check all the tests pass, and inspect a sampling of the results for consistency

Configuring the Generation Output

The most common reason to alter the generation is to add additional utility routines/enhanceements to the generated classes. To do this, edit on the one of the templates in the configuration directory - xx.java, where xx is the class name (may include containing class). You may also need to add to the imports in the configuration.ini file.