Prerequisites:

1. The machine should have JDK version 1.7 or above installed
2. The project having the custom request DTOs must be ready
3. Supporting jars as mentioned below
   1. com.ofss.digx.appcore.dto.jar – (available in ‘obapi.app.framework.ear’)
   2. com.ofss.fc.infra.jar – (available in ‘obapi.app.core.domain.ear’)
   3. com.ofss.fc.appcore.dto.jar – (available in ‘obapi.app.core.domain.ear’)
   4. Any other jars required for compilation of project containing custom request DTOs

Running the Utility:

This section explains step by step process to generate the validators using the utility.

Step 1: Copy the following artifacts from the <installer> to desired directory. This directory will be referred as <UTIL_DIR>.

1. validator_gen.bat (for Windows) OR validator_gen.sh (for Linux)
2. lib folder – (contains pre-built jars required for utility)

Add the supporting jars as mentioned in the prerequisites (point no 3) in the lib folder.

Step 2: Go to < UTIL_DIR > and open command prompt / terminal.

Execute following command:

1. For Linux

   ./validator_gen.sh <BIN_DIR> <UTIL_DIR> <PROJECT_DIR> <PACKAGE_NAME>

2. For Windows

   /validator_gen.bat <BIN_DIR> <UTIL_DIR> <PROJECT_DIR> <PACKAGE_NAME>.

Where,

<BIN_DIR>: Path where JDK bin is located (e.g. C:\Program Files\Java\jdk1.8.0_171\bin) (use “ if the path contains spaces)

<PROJECT_DIR>: path where request DTO project is located

<PACKAGE_NAME>: name of the package where the source of request DTOs is located

Consider following example

If the customized request DTOs are located in ‘D:\workspaces\trunk\com.ofss.digx.cz.app.xface\src \com…’

Then, < PROJECT_DIR > = ‘D:\workspaces\trunk’ and < PACKAGE_NAME > = ‘com.ofss.digx.cz.app.xface’

Step 3:

As a result of utility, a jar containing the compiled classes of validator files will be created in <UTIL_DIR>. Copy the jar file and paste in the EAR file where the jar of customized DTO classes is located. Deploy the EAR file in the application and restart the server.