Javaâ¢ Application Development on Linux - Dator

More documents

Recommendations

Info

$Permittivity/Dielectric Constant: Do The math - Dator$

198Chapter 8Know What You Have: CVSyour source. You should never need to mess with the files in the CVS directory;see the Cederqvist reference in Section 8.6 for more information aboutthese files.8.2.3 Normal UseThe typical use of CVS occurs after you’ve made some changes to your sourcecode. At some point, typically after the code compiles cleanly or after thechanges have been tested to some extent, you will want to commit your changesto the CVS repository. When you commit one or more files, they become thelatest version, the version that others get when they checkout or update themodule. To say it another way, when you commit, you make those changes apermanent part of the source repository, available to others.You can commit a single file at a time, like this:$ cvs commit Account.javaOr you can commit several files at a time, like this:$ cvs commit Account.java User.java Xyz.javaOr you can commit all the changes from a certain point in the filesystemhierarchy (e.g., the current directory) on down, like this:$ cvs commit(Specifying no files implies the current directory. You can also name a directoryexplicitly.)When you commit changes, CVS wants you to provide a bit of commentaryto explain what you’ve changed, to say something about this new version.The comment can be supplied on the command line, with the -m option:$ cvs commit -m "bug fix"If you don’t provide the -m parameter and its argument, CVS will invokeyour favorite editor (as specified in the environment variable CVSEDITOR orVISUAL or else EDITOR, in that order of precedence). The default, on Linuxsystems, is to invoke vi (see Figure 8.2). In the editor, you can type one or morelines of text; when you exit, the commit will continue to completion.
8.2 Source Control: Whys and Hows199Figure 8.2 CVS asking for commentary as part of a commitNOTEIf you quit the editor without writing your changes (in vi, that would be :q!) thenCVS will ask if you want to abort the entire commit. If you choose to abort, nochanges will be made to the repository. You’ll be right back to where you werejust before typing the cvs commit command.You will be able to see the comments associated with each version of thefile using the cvs log command (see Section 8.2.6).As you will want to provide brief but meaningful descriptions in thesecomments, it may be helpful to remind yourself what in fact has changed. Youcan see the differences between the version that you checked out and the file asit stands today by using the cvs diff command:$ cvs diff Account.javaHere, as in commit, you can name one or more files, or even a directory. CVSwill display what lines you’ve added, modified, or removed in each file.
Page 1 and 2:
Java Application
Page 3 and 4:
Java Application
Page 5:
To my mother, for her love of words
Page 8 and 9:
viiiContents1.41.51.6Chapter 22.12.
Page 10 and 11:
xContents5.65.75.85.95.105.115.125.
Page 12 and 13:
xiiContentsChapter 99.19.29.39.49.5
Page 14 and 15:
xivContentsChapter 1313.113.213.313
Page 16 and 17:
xviContentsChapter 1717.117.217.317
Page 18 and 19:
xviiiContents20.620.720.820.920.102
Page 21 and 22:
PrefaceJAVA AND LINUXWhy another bo
Page 23 and 24:
PrefacexxiiiFREE SOFTWARE AND JAVAG
Page 25:
Prefacexxvand Tyrrell Albaugh, who
Page 28 and 29:
xxviiiIntroductionIf you are an exp
Page 30 and 31:
xxxIntroductionThe Linux Newbie Pat
Page 33:
Part IGetting Started
Page 36 and 37:
4Chapter 1An Embarrassment of Riche
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
10Chapter 1An Embarrassment of Rich
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 65 and 66:
Chapter 2An Embarrassment of Riches
Page 67 and 68:
2.2 Eye to Eye with vi35of their co
Page 69 and 70:
2.2 Eye to Eye with vi37• L (“l
Page 71 and 72:
2.2 Eye to Eye with vi39In both cas
Page 73 and 74:
2.2 Eye to Eye with vi41• :7,.w!
Page 75 and 76:
2.2 Eye to Eye with vi431,$s/Tryout
Page 77 and 78:
2.3 Editors Galore45affected by thi
Page 79 and 80:
2.3 Editors Galore47has a huge lear
Page 81:
2.6 Resources49• fte is an editor
Page 84 and 85:
52Chapter 3An Experienced Programme
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
100Chapter 4Where Am I? Execution C
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
116Chapter 5The Sun Microsystems Ja
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
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 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181: 148Chapter 5The Sun Microsystems Ja
Page 200 and 201: 168Chapter 6The IBM Developer Kit f
Page 211 and 212: Chapter 7The GNU Compiler for Java(
Page 213 and 214: 7.4 Compiling Our Simple Ap
Page 215 and 216: 7.4 Compiling Our Simple Ap
Page 217 and 218: 7.5 Options and Switches1857.5OPTIO
Page 219 and 220: 7.9 What You Still Don’t Know187o
Page 221 and 222: Chapter 8Know What You Have:CVSSour
Page 223 and 224: 8.2 Source Control: Whys and Hows19
Page 229: 8.2 Source Control: Whys and Hows19
Page 243 and 244: 8.3 A GUI: jCVS211and the differenc
Page 245 and 246: 8.4 Review213Figure 8.7 jCVS checko
Page 247 and 248: Chapter 9Ant:An IntroductionAnt 1 i
Page 249 and 250: 9.3 Obtaining and Installing Ant217
Page 251 and 252: 9.3 Obtaining and Installing Ant219
Page 253 and 254: 9.4 A Sample Ant Buildfile221standa
Page 255 and 256: 9.4 A Sample Ant Buildfile2239.4.2.
Page 257 and 258: 9.4 A Sample Ant Buildfile225$ antB
Page 259 and 260: 9.4 A Sample Ant Buildfile227debugI
Page 261 and 262: 9.4 A Sample Ant Buildfile229Exampl
Page 263 and 264: 9.4 A Sample Ant Buildfile231Runnin
Page 265: 9.7 Resources233• O’Reilly has
Page 268 and 269: 236Chapter 10Integrated Dev
Page 280 and 281:
248Chapter 10Integrated Dev
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 295 and 296:
Chapter 11Balancing Acts:An Imagina
Page 297 and 298:
11.3 How to Develop Software265soft
Page 299 and 300:
11.4 What Makes a Good Requirement2
Page 301 and 302:
11.6 Requirements for the Budget <s
Page 303 and 304:
11.6 Requirements for the Budget <s
Page 305 and 306:
11.7 Documenting, Prototyping, and
Page 307 and 308:
11.7 Documenting, Prototyping, and
Page 309 and 310:
11.11 Exercises277• http://www.pr
Page 311 and 312:
Chapter 12Analysis and Design:Seeki
Page 313 and 314:
12.4 Finding the Objects281Accounta
Page 315 and 316:
12.5 Finding the Methods and Attrib
Page 317 and 318:
12.6 Essential and Nonessential285
Page 319 and 320:
12.7 Analysis Paralysis287• Class
Page 321 and 322:
12.12 Resources28912.9CORE CLASSESS
Page 323 and 324:
12.12 Resources291if (dbConn != nul
Page 325:
12.13 Exercises293Example 12.2 The
Page 328 and 329:
296Chapter 13JUnit: Automating Unit
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 347 and 348:
Chapter 14Storing the DataIn this c
Page 349 and 350:
14.5 Oracle, PostgreSQL, MySQL31714
Page 351 and 352:
14.7 Beyond the Basics319files, and
Page 353 and 354:
14.7 Beyond the Basics321Hibernate
Page 355 and 356:
14.9 Setting Up PostgreSQL for Budg
Page 357 and 358:
14.10 Review32514.9.4 Straight JDBC
Page 359 and 360:
Chapter 15Accessing the Data:An Int
Page 361 and 362:
15.3 Making Connections329These thr
Page 363 and 364:
15.3 Making Connections331Example 1
Page 365 and 366:
15.4 Querying Data333// queryString
Page 367 and 368:
15.5 Getting Results335TIPThe case
Page 369 and 370:
15.9 Resources337We haven’t cover
Page 371:
Part IIIDevelopingGraphical User In
Page 374 and 375:
342Chapter 16Getting in the Swing o
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
Page 406 and 407:
Page 408 and 409:
Page 410 and 411:
378Chapter 17Other Ways: Alternativ
Page 412 and 413:
Page 414 and 415:
Page 416 and 417:
Page 418 and 419:
Page 420 and 421:
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Page 433:
Part IVDevelopingWeb Interfaces
Page 436 and 437:
404Chapter 18Servlets: Java Pressed
Page 438 and 439:
Page 440 and 441:
Page 442 and 443:
Page 444 and 445:
Page 446 and 447:
Page 448 and 449:
Page 450 and 451:
Page 452 and 453:
Page 455 and 456:
Chapter 19JSP:Servlets Turned Insid
Page 457 and 458:
19.2 Servlets Turned Inside Out: JS
Page 459 and 460:
19.3 How to Write a JSP App
Page 461 and 462:
Page 463 and 464:
Page 465 and 466:
Page 467 and 468:
Page 469 and 470:
Page 471 and 472:
19.5 Review439into JSP files. The m
Page 473:
19.8 Exercises441To get it straight
Page 476 and 477:
444Chapter 20Open Source Web <stron
Page 478 and 479:
Page 480 and 481:
Page 482 and 483:
Page 484 and 485:
Page 486 and 487:
Page 488 and 489:
Page 490 and 491:
Page 492 and 493:
Page 494 and 495:
Page 496 and 497:
Page 498 and 499:
Page 500 and 501:
Page 503:
Part VDevelopingEnterprise Scale So
Page 506 and 507:
474Chapter 21Introduction to Enterp
Page 508 and 509:
Page 510 and 511:
Page 512 and 513:
Page 514 and 515:
Page 516 and 517:
Page 518 and 519:
Page 520 and 521:
Page 522 and 523:
Page 524 and 525:
Page 526 and 527:
494Chapter 22Building an EJBclasses
Page 528 and 529:
496Chapter 22Building an EJBwhich,
Page 530 and 531:
498Chapter 22Building an EJBExample
Page 532 and 533:
500Chapter 22Building an EJBExample
Page 534 and 535:
502Chapter 22Building an EJBIf you
Page 537 and 538:
Chapter 23Deploying EJBsIn this cha
Page 539 and 540:
23.2 Lend Me Your EAR: Enterprise P
Page 541 and 542:
Page 543 and 544:
Page 545 and 546:
Page 547 and 548:
23.3 Deploying the EAR515automatic
Page 549 and 550:
23.4 Maintaining a Distributed <str
Page 551:
23.8 Resources519Ant and CVS and ho
Page 554 and 555:
522Chapter 24Parting ShotsThe three
Page 556 and 557:
524Chapter 24Parting ShotsPrentice
Page 558 and 559:
526Appendix AASCII ChartInt Oct Hex
Page 560 and 561:
528Appendix BA Java Swing GUI for B
Page 562 and 563:
Page 564 and 565:
Page 566 and 567:
Page 568 and 569:
Page 571 and 572:
Appendix CGNUGeneral Public License
Page 573 and 574:
C.2 Terms and Conditions for Copyin
Page 575 and 576:
C.2 Terms and Conditions for Copyin
Page 577 and 578:
C.3 NO WARRANTY545of this License,
Page 579:
C.5 How to Apply These Terms to You
Page 582 and 583:
550Index$ (dollar)in format fields,
Page 584 and 585:
552Indexbreak statement, 67, 74-75b
Page 586 and 587:
554IndexCVS_RSH environment variabl
Page 588 and 589:
556IndexFfail(), 307false constant,
Page 590 and 591:
558IndexIBM, 236, 377, 518Common Pu
Page 592 and 593:
560IndexJNDI (Java Naming and Direc
Page 594 and 595:
562IndexNetBeans (continued)running
Page 596 and 597:
564IndexScrollBar class, 385search
Page 598 and 599:
566IndexTable class, 386, 394-395ta
show all

Javaâ¢ Application Development on Linux - Dator

Create successful ePaper yourself

Delete template?

Save as template?

Javaâ¢ Application Development on Linux - Dator