Generated Files
HydraExpress generates server and client-side code, sample applications, configuration files, makefiles, MSVC project files, and documentation into a directory DayOfWeekExample, using the options included in the example-project.xml file. (HydraExpress supports only file paths without spaces, so when naming your project, do not include spaces, since HydraExpress uses the project name as a basis for the name of the code generation directory.)
The project files are generated into several subdirectories, according to HydraExpress’ standard code generation directory hierarchy. For more information on the directory structure, see The Generated Project Directory.
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.
Table 5 – Files generated for DayofWeek example 
Directory
Files
Description
DayOfWeekExample/
DayOfWeekExample.xml
The project file, named according to the project name, defining all project elements (options, configurations, schemas, WSDLs, etc.). See The Project File.
 
makefile
makefile_debug
Project-level makefiles. Calls all makefiles in subdirectories. Overwrite-protected.
 
makefile.include
Include makefile. Contains all makefile compiler and linker options. Edits to this file cascade down to all makefiles. Overwrite-protected.
 
DayOfWeekExample.sln
MSVC solution file. Generated for Windows platforms.
 
deployDebug.bat
deployRelease.bat
Convenience debug and release deployment batch files generated for use with MSVC projects.
    app/
makefile
makefile_debug
Makefiles. Builds contents of app/ directory.
Overwrite-protected.
        /client
DayOfWeekPortClient.cpp
Sample client implementation using the client proxy. Overwrite-protected.
 
makefile
makefile_debug
Makefiles. Builds contents of app/client directory. Overwrite-protected.
 
DayOfWeekPortClient.vcproj
MSVC project file generated for Windows platforms.
        /server
DayOfWeekPortTypeImp.cpp
DayOfWeekPortTypeImp.h
Sample service implementation and header files. Overwrite-protected.
 
makefile
makefile_debug
Makefiles. Builds contents of app/server directory. Overwrite-protected.
 
DayOfWeekPortServiceSample.vcproj
MSVC project file generated for Windows platforms.
    codegen/
makefile
makefile_debug
Makefiles. Builds contents of codegen/ directory. Overwrite-protected.
        /client
DayofWeekBindingProxy.cpp
Implementation file for the generated client proxy class. Defines the methods for the operations defined in the WSDL file.
 
makefile
makefile_debug
Makefiles. Builds contents of codegen/client directory. Overwrite-protected.
 
DayOfWeekBindingClientLibrary.vcproj
MSVC project file generated for Windows platforms.
        /server
DayOfWeekBindingSkeleton.cpp
DayOfWeekPortTypeBase.cpp
Implementation files for the class that handles messaging and the base class for the server-side implementation.
 
makefile
makefile_debug
Makefiles. Builds contents of codegen/server directory. Overwrite-protected.
 
DayOfWeekPortService.vcproj
MSVC project file generated for Windows platforms.
    conf/
transports.xml
client-transports.xml
Configuration files for:
1. Server and client transports
 
dayofweek_handlers.xml
2. Server-side handlers to support handler chaining and configuration
 
client-handlers.xml
3. Client-side handlers containing default client logger
 
dayofweek_objects.xml
4. All named objects required by this service. These are registered and created when the Agent is started.
 
dayofweek_web.xml
5. Service Descriptor XML file for the service
 
makefile
makefile_debug
Deployment makefiles. Overwrite-protected.
    docs/
index.html
The generated documentation. Use index.html as the entry point to all docs contained in the docs subdirectories.
    include/
 
Header files, as follows:
        /DayOfWeekExample
Subdirectory by project name
 
DayOfWeekBindingProxy.h
1. Client proxy class
 
DayOfWeekBindingSkeleton.h
2. Class that handles messaging
 
DayOfWeekPortTypeBase.h
3. Base class for the server-side implementation
Note that the directories bin and lib are empty at code generation, but will include the .exe and .dll files, or the .lib or .so files after the project build, depending on your platform.