Getting Startedwith pureQuery

Chapter 11 – Annotated-Method Programming Style 231
Listing 11.29- Changes to the displayEmployeeInformation method to update a
last name
// Update the first name in the database
updateCount = data.updateEmployeeFirstName (employee);
Listing 11.30 -Changes to the displayEmployeeInformation method to update a
first name
11.6.2.3 Test the "Change Employee Information" screen
Save and test your application. Supply 000030 to login as Sally Kwan. On the main
menu, select option 2 to change information about Sally. Then, return to the main menu
and select option 4 to go to the “Company Employees” screen and find Heather A.
Nicholls, one of the employees that Sally manages. View information about Heather, and
then change information for her.
11.7 Tooling Support for Annotated Methods and Generated Code
General pureQuery tooling support was introduced starting in Chapter 3. The following
features provide support that is specifically tailored to code generated using the pureQuery
annotated method API.
11.7.1 Generating XML file to override the SQL statements in interfaces
When the implementation class is generated by the pureQuery Generator for an interface
that defines annotated methods, you can use an XML file to specify or override the SQL
statements that those methods use. You can also use the same XML file to override how
the columns in a database object, such as a table or view, map to the properties of a bean.
To specify an XML configuration file, use the xmlFile option when you invoke the
pureQuery Generator.
You might want to override SQL statements in an XML file when you want to use the same
interface in another application that runs against a different database. For example,
assume that your interface contains the following method:
@Select(sql=”SELECT CUSTID, NAME FROM Customer WHERE STOREREGION=?1”)
Iterator getCustomersInRegion(int r)
In the XML configuration file for the other application, you can override the SQL like this: