-
TEMPLATE
Archetype Template Translator Project
One way to start developing a custom translator is to create a project using the Teiid archetype template. When the project is created from the template, it will contain the essential classes (i.e., ExecutionFactory) and resources for you to begin adding your custom logic. Additionally, the maven dependencies are defined in the pom.xml so that you can begin compiling the classes.
Note
|
The project will be created as an independent project and has no parent maven dependencies. It’s designed to be built independent of building Teiid. |
You have 2 options for creating a translator project; in Eclipse by creating a new maven project from the arche type or by using the command line to generate the project.
Create Project in Eclipse
To create a Java project in Eclipse from an arche type, perform the following:
-
Open the JAVA perspective
-
From the menu select File –> New —> Other
-
In the tree, expand Maven and select Maven Project, press Next
-
On the "Select project name and Location" window, you can accept the defaults, press Next
-
On the "Select an Archetype" window, select Configure button
-
Add the remote catalog: https://repository.jboss.org/nexus/content/repositories/releases/ then click OK to return
-
Enter "teiid" in the filter to see the Teiid arche types.
-
Select the translator-archetype v10.0.0, then press Next
-
Enter all the information (i.e., Group ID, Artifact ID, etc.) needed to generate the project, then click Finish
The project will be created and name according to the *ArtifactID*.
Create Project using Command Line
Note
|
make sure the https://repository.jboss.org/nexus/content/repositories/releases/ repository is accessible via your maven settings. |
To create a custom translator project from the command line, you can use the following template command:
mvn archetype:generate \
-DarchetypeGroupId=org.teiid.arche-types \
-DarchetypeArtifactId=translator-archetype \
-DarchetypeVersion=${archetypeVersion} \
-DgroupId=${groupId} \
-DartifactId=translator-${translator-type} \
-Dpackage=${package} \
-Dversion=${version} \
-Dtranslator-type=${translator-type} \
-Dtranslator-name=${translator-name}
-Dteiid-version=${teiid-version}
-DarchetypeGroupId - is the group ID for the arche type to use to generate
-DarchetypeArtifactId - is the artifact ID for the arche type to use to generate
-DarchetypeVersion - is the version for the arche type to use to generate
-DgroupId - (user defined) group ID for the new translator project pom.xml
-DartifactId - (user defined) artifact ID for the new translator project pom.xml
-Dpackage - (user defined) the package structure where the java and resource files will be created
-Dversion - (user defined) the version that the new connector project pom.xml will be
-Dtranslator-type - (user defined) the translator type that's used by Teiid when mapping the physical source to the translator to use
-Dtranslator-name - (user defined) the translator name thats used for name the java class names
-Dteiid-version - [optional] the Teiid version the connector will depend upon, if not specified will default
-
this is an example of the template that can be run:
mvn archetype:generate \
-DarchetypeGroupId=org.teiid.arche-types \
-DarchetypeArtifactId=translator-archetype \
-DarchetypeVersion=10.0.0 \
-DgroupId=org.example \
-DartifactId=translator-type \
-Dpackage=org.example.translator.type \
-Dversion=0.0.1-SNAPSHOT \
-Dtranslator-type=type \
-Dtranslator-name=Type \
-Dteiid-version=10.3.0
When executed, you will be asked to confirm the properties
Confirm properties configuration: groupId: org.example artifactId: translator-type version: 0.0.1-SNAPSHOT package: org.example.translator.type teiid-version: 10.3.0 translator-name: Type translator-type: type Y: : y
type Y (yes) and press enter, and the creation of the translator project will be done
Upon creation, a directory based on the *artifactId* will be created, that will contain the project. 'cd' into that directory and execute a test build to confirm the project was created correctly:
mvn clean install
This should build successfully, and now you are ready to start adding your custom code.