Simple Schema Building Tools is a tool to create a tailored package with just the schema you want using your favorite binding package using the OpenTravel schema.
In just few simple steps, you will have a custom built schema package ready to use.
Choose your preferred tool. The project currently supports JiBX, JAXB, and XMLBeans.
Choose your preferred schema. Out of the box support is provided for 2013A, 2012B and 2012A, 2011B, 2011A, 2010B, 2010A, 2009A, 2008B, 2008A, 2007B, 2007A, 2006B, 2006A, and 2004B. Adapting your project to older schema only requires a few simple changes to your project file
Try it. it's easy:
Step 1: Create your packaging project from this archetype.
Here is a sample command line for creating a hotel interface project with this tool:
mvn archetype:generate -DarchetypeGroupId=net.sourceforge.ota-tools.schema \
-DarchetypeArtifactId=ota-tools-schema-archetype -DarchetypeVersion=1.1.6 \
-Dschema-version=2013A -Dtravel-segment=hotel -Dbinding-engine=jaxb \
-DgroupId=org.opentravel -DartifactId=opentravel-2013a-hotel \
-Dversion=1.0.0 -Dpackage=org.opentravel -DinteractiveMode=false
The backslashes make this long command fit on a single line. Ignore any warnings from the build.
The schema-version can be 2013A, 2012B, 2012A, 2011B, 2011A, 2010B, 2010A, 2009A, 2008B, 2008A, 2007B, 2007A, 2006B, 2006A, or 2004B. The binding-engine can be jibx, jaxb, or xmlbeans. The travel-segment should equal all, air, cruise, destactivity, dynamicpkg, golf, hotel, insurance, loyalty, ping, pkg, profile, rail, misc, tour, travelitinerary, veh, fastrez, or codetable.
The groupId, artifactId, version are standard maven project parameters. The package parameter is the java package of the resulting code.
Step 2: Create your module:
cd my-project-name (in my example my-project-name is opentravel-2012a-hotel)
Now you're ready to use your project to write code. Just include the artifact in your project. In my case, I would add this to my pom file:
Step 3: Start writing code.
If you want to create a custom bundle with just the messages that you use, that is easy too. Do step 1 and create a project with all the schema, then edit the ota.xsd file in the project to include just the messages that you need. Finish the rest of the steps and you have a custom bundle!
Now you can get to work on the fun stuff, writing your messaging code!