Generated Files

HydraExpress Components : XML Binding Development Guide : PART II Code Generation Examples : Basic Purchase Order Example : Generating Code from Schema : Generated Files

Generated Files

Table 2 lists the generated files for the Basic example.

NOTE: 	Files that are overwrite-protected are generated with a “.sample” extension if a file exists in the code generation directory of the same name. See “Overwrite Protection,” in the HydraExpress Web Service Development Guide.

Table 2 – Generated files for an XML Schema
Directory	Files	Description
basicExample\	basicExample.xml	Project file, named according to the project name, and defining all project elements.
	makefile makefile_debug	Project-level makefiles. Calls all makefiles in subdirectories. Overwrite protected.
	basicExample.sln	Windows only. MSVC projects and solutions. See description in “Generator Options,” in the HydraExpress Web Service Development Guide.
	make.include	Master makefile configuration file. Contains all compiler and linker options. Edits to this file cascade to all makefiles, allowing you to make just one change instead of editing each makefile individually.
	deployDebug.bat deployRelease.bat	Convenience debug and release deployment batch files generated for use with MSVC projects.
app\	makefiles MSVC project files	Makefiles and MSVC project files for the app directory. Overwrite protected.
data\	po_main.cpp or po_main.cpp.sample	Sample application file.Overwrite protected.
codegen\	makefiles MSVC project files	Makefiles and MSVC project files for the codegen directory. Overwrite protected.
data\	makefiles MSVC project files	Makefiles and MSVC project files for the data directory. Overwrite protected.
po\	Items.cpp ItemsItem.cpp PurchaseOrder.cpp PurchaseOrderType.cpp USAddress.cpp	Source files for the datatype classes. Since the schema defines a namespace prefix, these files are placed in a subdirectory named for the prefix.
	[poStatics.cpp]	A poStatics.cpp class is generated only if the noTopLevelClasses property is specified at code generation. See Working Without Top-Level Element Classes.
	ItemsMarshal.cpp ItemsItemMarshal.cpp PurchaseOrderTypeMarshal.cpp USAddressMarshal.cpp	Marshaling classes for each datatype class.
docs\	index.html	HTML documentation files.
include\ projectname\ namespaces\	Items.h ItemsItem.h PurchaseOrder.h PurchaseOrderType.h USAddress.h ItemsMarshal.h ItemsItemMarshal.h PurchaseOrderTypeMarshal.h USAddressMarshal.h	Header files for the datatype classes, organized in subdirectories based on project name and namespace. (If the schema defines a namespace prefix, these files are placed in a subdirectory named for the prefix.)
	[poStatics.h]	A poStatics.h header is generated only if the noTopLevelClasses property is specified at code generation.