Getting Startedwith pureQuery

More documents

Recommendations

Info

240 Getting Started with pureQuery D. Specify the interface to a method named generateImplementationClass in the com.ibm.pdq.runtime.Data interface. 6. If you want to customize how pureQuery generates the implementation classes for your interfaces, you can specify the options that you want to use in an options file. In IBM Optim Development Studio, what is the name of that file? A. Default.bindProps B. pdq.properties C. Default.genProps D. generator.properties 7. When you run an annotated-method style application with the property pdq.executionMode set to the value STATIC, what happens if your application executes an SQL statement that is not bound in the database? A. The SQL statement executes statically B. The SQL statement executes dynamically C. pureQuery throws an exception D. None of the above 8. For an interface of annotated methods, the implementation classes that pureQuery generates implements another interface. What is the other interface? Why is this helpful? 9. What is one way in which you can close the java.sql.Connection object associated with an instance of an interface? 10. What are some of the benefits of using the annotated method style? 11. What would a user need to do in order to generate their own customized dataaccess code using the pureQuery tooling? 11.12 Exercise In hrm.inProgress.pdqMethodStyle.HumanResourcesManager, the method displayEmployeeReportChain creates the “Employee Report Chain” screen. This screen needs to display the employees that report to the specified employee, as well as the specified employee’s manager. Look for the comments // TODO: Add pureQuery code here. in the method and add the necessary pureQuery code. There are two places in displayEmployeeReportChain that you need to update; one needs a new annotated method, and the other can use one of the existing annotated methods. Comments in the code show the SQL statements that you can use for the operations. The completed
Chapter 11 – Annotated-Method Programming Style 241 version of the code is available in hrm.completed.pdqMethodStyle.HumanResourcesManager and hrm.completed.pdqMethodStyle.HumanResourcesData. As described in Section 4.1.5, the “Employee Report Chain” screen displays the employees that report to a specified employee, as well as the manager of the specified employee. Add the necessary pureQuery code to hrm.inProgress.pdqMethodStyle.HumanResourcesManager and hrm.inProgress.pdqMethodStyle.HumanResourcesData to finish developing this screen. • The method displayEmployeeReportChain creates the “Employee Report Chain” screen. • For your reference, the completed version of the code is available in hrm.completed.pdqMethodStyle.HumanResourcesManager and hrm.completed.pdqMethodStyle.HumanResourcesData. • Locate the code in Listing 11.33 in the displayEmployeeReportChain method. You will need to add code that calls the method selectEmployeeManager that you added in Section 6.5.2.1, shown in Listing 11.17. // Get the manager of this employee. // TODO: Add pureQuery code here. EmployeeBean manager = null; Listing 11.33 - You need to add a call to the annotated method shown in Listing 11.17. • Locate the code in Listing 11.34 in the displayEmployeeReportChain method. You need to add a call to a new annotated method that you add. The new annotated method needs to query the database for the employees that the specified employee directly manages. You can use the SQL statement in Listing 10.29, which is described in the Exercise 10.9. Since you are adding a new annotated method, you need to use the DYNAMIC execution mode, or you need to rebind the interface. // Search the database for all the employees that this employee // directly manages and create a list of the employees managed by // this employee. // TODO: Add pureQuery code here. List managedEmployees = null; Listing 11.34 - You need to add a call to an annotated method that gets the employees managed by the specified employee
Page 3 and 4:
G E T T I N G S T A R T E D W I T H
Page 5 and 6:
Notices This information was develo
Page 7:
Trademarks IBM, the IBM logo, DB2,
Page 10 and 11:
10 Getting Started with pureQuery 3
Page 12 and 13:
12 Getting Started with pureQuery C
Page 14 and 15:
Page 16 and 17:
16 Getting Started with pureQuery C
Page 18 and 19:
18 Getting Started with pureQuery m
Page 20 and 21:
20 Getting Started with pureQuery T
Page 22 and 23:
22 Getting Started with pureQuery K
Page 24 and 25:
24 Getting Started with pureQuery A
Page 27 and 28:
1 Chapter 1 - Introduction to pureQ
Page 29 and 30:
Chapter 1 - Introduction to pureQue
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
2 Chapter 2 - Installing pureQuery
Page 47 and 48:
Chapter 2 - Installing pureQuery (O
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61:
PART II - TOOLING
Page 66 and 67:
66 Getting Started with pureQuery F
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
72 Getting Started with pureQuery t
Page 74 and 75:
74 Getting Started with pureQuery A
Page 76 and 77:
76 Getting Started with pureQuery T
Page 78 and 79:
78 Getting Started with pureQuery a
Page 80 and 81:
80 Getting Started with pureQuery r
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
86 Getting Started with pureQuery Y
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
92 Getting Started with pureQuery D
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
98 Getting Started with pureQuery
Page 100 and 101:
Page 102 and 103:
Page 105 and 106:
PART III - SECURITY, PERFORMANCE, A
Page 107 and 108:
6 Chapter 6 - The Client Optimizer:
Page 109 and 110:
Chapter 6 - The Client Optimizer: p
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
7 Chapter 7 - The StaticBinder Util
Page 139 and 140:
Chapter 8 - Extended Insight 139 No
Page 141 and 142:
7.2.2.3 Changes to pureQueryXml fil
Page 143 and 144:
Chapter 8 - Extended Insight 143 Fi
Page 145 and 146:
Chapter 8 - Extended Insight 145 Fi
Page 147 and 148:
Chapter 8 - Extended Insight 147 -u
Page 149 and 150:
Chapter 8 - Extended Insight 149 7.
Page 151 and 152:
Chapter 8 - Extended Insight 151 ne
Page 153:
Chapter 8 - Extended Insight 153 11
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 169 and 170:
9 Chapter 9 - Persistence Framework
Page 171 and 172:
9.1.1.1 JPA Chapter 9 - Persistence
Page 173 and 174:
Chapter 9 - Persistence Frameworks
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191: 190 Getting Started with pureQuery
Page 243 and 244: 12 Chapter 12 - Stored Procedures T
Page 245 and 246: Chapter 12 - Stored Procedures 245
Page 261 and 262: 13 Chapter 13 - Handlers In this ch
Page 263 and 264: Chapter 13 - Handlers 263 Figure 13
Page 265 and 266: Chapter 13 - Handlers 265 SELECT *
Page 267 and 268: Chapter 13 - Handlers 267 construct
Page 269 and 270: 13.4.1 Writing a ResultHandler impl
Page 271 and 272: Chapter 13 - Handlers 271 functiona
Page 273 and 274: Chapter 13 - Handlers 273 Listing 1
Page 275 and 276: Chapter 13 - Handlers 275 package h
Page 277: A. In a getData method in the com.i
Page 281 and 282: 14 Chapter 14 - Best Practices In t
Page 283 and 284: Chapter 14 - Best Practices 283 @Se
Page 285 and 286: Chapter 14 - Best Practices 285 Fig
Page 287 and 288: 15 Chapter 15 - pureQuery and pureX
Page 289 and 290: Chapter 15 - pureQuery and pureXML
Page 291 and 292:
Chapter 15 - pureQuery and pureXML
Page 293:
Chapter 15 - pureQuery and pureXML
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 305 and 306:
A Appendix A - Solutions to the rev
Page 307 and 308:
Appendix A - Solutions to the revie
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
B Appendix B - Understanding the Sa
Page 315 and 316:
B.1.3 The “Employee Information
Page 317 and 318:
Appendix C - Up and Running with DB
Page 319 and 320:
B.1.6 The “Company Employees” s
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
C.4.1 IBM Optim Development Studio
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 355 and 356:
E Appendix E - Options Files This a
Page 357 and 358:
Appendix E - Options files 357 comm
Page 359:
Appendix E - Options files 359 In b
Page 363 and 364:
Resources Web sites 1. pureQuery pl
show all

Getting Startedwith pureQuery

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?