The db-import.dtd is the DTD that is automatically created (by the Ant Build) based on the schema that is provided by the schema tag. The DTD is always called dbname-import.dtd, where dbname is the name specified in the schema tag.

The root tag for the initial-and-test-data.xml is dal.

The root dal tag may contain one or more tags named as table-name (book-info in this case). Note that the underscore "_" in the original table name "book_info" (specified by schema tag in the project file) is replaced with a hyphen "-". The table field names become the attributes for the table-name tag (id, name, author, genre and isbn in this case). The values you provide for these fields are stored in the corresponding hsql table.

Defining the Axiom Data Access Layer namespace prefix dal.

Defines the output of the XSL (XML in this case).

Defines the default template.

The template that you will use in your XML file. This template receives, through the parameter count, the number of records to be added. It calls another custom template named "iterate-one". The value of count parameter is also sent to the called template.

This is the iterate-one template which is called by the generate-info-records template. It generates the values for all the fields of Book_Info table.

The book-info XML records are generated using the value of parameter x, which changes on every iteration of the iterate-one template.

This tag is responsible for recursively calling the iterate-one template. It checks the value of the parameter x and, if it is greater than 1, decreases it by one to call the iterate-one template with this new value.

The xdm-transform processing instruction tells Sparx to filter special tags through the XSLT before processing.

Calling the the template from XSL to generate 100 test records for Book_Info table.

All the static in Axiom must belong to a statement package represented by queries XML tag. The statement package is identified by its name (books in the above example). You can define multiple packages within your application's project.xml file.

A static query is defined (with or without bind parameters) by using the query tag. Each query is identified by its name (get-all-books in the above example).

	Note
	The namespace of a query is always queryPkg.queryName. This means you can have more than one queries with same name if each of them belongs to a different query package.

The static SQL (with or without bind parameters) is declared under the query tag. The query in this example declares a join on the Book_Type and Book_Info tables using the genre (from Book_Info) and id (from Book_Type) fields.

Each query tag contains a presentation tag associated with it. This tag defines presentation aspects of the query.

The panel tag is used to display a panel of given height. This panel serves as a container for the displayed query result.

The frame tag defines a frame to be drawn around the query result. The heading attribute is assigned a value using static value source.

A report is a way to customize the output of a SQL statement on the page.

	Note
	Each SQL statement may have any number of report tags as necessary. That way, a single statement can be viewed differently depending upon what context it’s being called in.

You can declare a set of actions for your query's result. This is done using the actions tag. These actions provide a way to perform different functions on the displayed query result. Sparx has pre-defined action types for performing add, edit and delete operations on the selected record within your query result.

The action tag is used to define individual actions (add in this case). The action tag may specify a redirect attribute to automatically redirect to another page whenever it is chosen. The name of the redirect page is supplied using the page-id value source.

Declaring edit action. You may also supply parameters and their values within the redirect URL (selected record's id field in this case).

Any ${XXX} specifies a dynamic replacement. Usually, value sources are used within the brackets but when the dynamic replacement definition is used within a report definition (declared using report tag), you can insert a number within the brackets to indicate the column index of the report. In the above example, ${0} is used to indicate that it should be replaced with the value of the first column of current row.

Declaring the delete action with redirect attribute pointing to the delete page.

Every SQL report contains column tags that are used to customize the appearance of a particular column or, more accurately, a particular field. You may also specify a redirect page URL (edit page in this case).

All query definitions are declared using the query-defn tag and are uniquely identified with a name (books in this case).

Each query definition contains one ore more field tags that declare the selectable fields. The field tags are specified so that Axiom knows what fields the user should be allowed to select. Query definition fields may come from a mix of tables so long as they have appropriately defined join attribute values. The value of the join attribute is a reference to a join tag later on in the query definition (BookInfo and bookType in this case).

	Note
	In the context of the final SQL statement that Sparx generates, the field tags become a part of the select clause. i.e. the part of a select statement that determines which fields need to be returned.

The column attribute of field tag contains the field name (name in this case) as defined in the schema table (Book_Info in this case). The name attribute is used to define a different name for the schema table field (genre_id and genre, respectively, in this case).

The join tag is used to let the query definition know of the list of tables and joins. This is necessary to be able to get all the fields that are a part of the query definition. Each join tag is uniquely identified through its name. The table attribute contains the schema table name whereas the condition attribute defines the join condition.

	Note
	In the context of the final SQL statement that Sparx generates, the join tags become a part of the where clause to signify the relationships between tables (if any exists).

The search dialog and search field results are declared under a presentation tag in the query-defn hierarchy.

The select-dialog tag is essentially a dialog embedded inside a query definition. The purpose of this dialog is to provide a user interface for the query definition. Each select-dialog is uniquely identified through its name.

	Note
	One query definition can have multiple select-dialogs declarations.

The allow-debug attribute of select-dialog tag is used to specify the query debug option. If it is set to "yes" (as in this example), a debug check box is displayed (with the caption View Generated SQL). When this checkbox is checked and the dialog is submitted, the generated SQL with its bind parameters is displayed for debugging purposes instead of execution of the generated SQL

The hide-output-dests attribute is used to give the user several output options: HTML output (pageable report and row count per page), CSV output format, tab delimited format. This is done by setting the value of this attribute to "no". The hide-readonly-hints attribute is used to show or hide the field hints (as is the case in this example).

The frame tag is used to draw a frame, with appropriate heading, around the search dialog.

The first part of a select-dialog is a declaration of all the fields (and their corresponding UI representations) that the select-dialog will use for user input. Each field has associated name and caption attributes. The genre field is declared to be a "select". The choices for this field are populated with the values from Book_Type table using schema-enum value source.

The second part of a select-dialog is a select section which has two parts in itself. The select component is what determines which of the select-dialog’s declared fields are actually displayed in the dialog for this select-dialog. It also determines how each field will be interpreted by the query definition engine once the dialog is submitted. The select tag is uniquely identified through its name (test in this case).

The display tags have one attribute, field, which points to the name of a field declared in the main query definition.

The condition tags determine how the data input from the select-dialog will be interpreted by the query definition engine. Basically, it defines the search criteria.

Each condition tag represents a condition on a field specified by the field attribute. The allow-null attribute of the condition tag determines the behavior of the query definition engine if this field is left empty when the dialog is submitted. The value of this attribute is set to “no” in this case. That is why the select generated will omit the field if the corresponding dialog field happens to be empty. The comparison attribute of the condition tag describes the relational operator to use ("equals" in this case).

The value attribute of the condition tag describes the field from the main query definition (book_id in this case) with which this select-dialog field (book_id in this case) is to be compared. The select-dialog field is mentioned using the field value source.

The connector attribute determines how many field criteria each record in the database has to match before it is selected. In this example, all the fields have a connector value of “and” thus specifying that a record would have to match all the field criteria to be selected in the final result.

The result of this dynamically generated and executed query can be configured in different ways using presentation tag hierarchy.

The report tag customizes the displayed query result fields.

Each report tag contains column tags to customize the display of individual query result fields. You may also provide a redirect URL which a column through the redirect attribute. In this example, the ID field of the book record in the displayed result points to the Edit Book page. Clicking on this link will open the Edit Book page with the dialog fields populated with the selected book's information.