Index

A C D E G I L M P R S T U W

A

Apache Ant build tool, 2.1.1

architecture and design guidelines, 3.2

AntiPatterns, 3.2.1

designing for extension, 3.2.2

C

Central Office application

build, 2.1.4

coding your first feature, 8

before you begin, 8.1

common frameworks, 3.3

exception handling, 3.3.3

logging, 3.3.2

D

development environment, 2

preparation, 2.2.1

prerequisites, 2.1.2

setup, 2.2.2

build the database, 2.2.2.2

install Point-of-Service, 2.2.2.1

domain package, 5.3

database, 5.3.2

retail domain, 5.3.1

E

extending transaction search, 8.2

add business logic to commerce service, 8.2.9

add new criteria to the service, 8.2.9.2

create a class to create the criteria object, 8.2.9.1

handle SQL code changes in the service bean, 8.2.9.3

configure action mapping, 8.2.5

add code to handle new fields to search transaction form, 8.2.5.1

add method to base class, 8.2.5.3

create a Struts action class, 8.2.5.2

item quantity example, 8.2.1

verify application manager implementation, 8.2.7

web UI framework, 8.2.3

add strings to properties files, 8.2.3.2

configure the sideNav tile, 8.2.3.3

create a new JSP file, 8.2.3.1

extensibility, 16.1

adding a new dataset, 16.1.2

adding new dataset type, 16.1.4

adding new table to existing dataset, 16.1.1

adding more tables to existing dataset types, 16.1.1.1

changing Oracle Retail Point-of-Service client database vendor, 16.1.5

configuring schedule for dataset producer and consumer, 16.1.3

configure dataset consumer, 16.1.3.2

configure dataset producer, 16.1.3.1

extension guidelines, 5, 6

conventions, 5.1

directory paths, 5.1.4

filename conventions, 5.1.2

modules, 5.1.3

terms, 5.1.1

internationalization, 5.2.3.1

pos package, 5.2

other, 5.2.3

tour, 5.2.1

UI framework, 5.2.2

extracting source code, 1

G

general development standards, 3

basics, 3.1

avoiding common Java bugs, 3.1.2

formatting, 3.1.3

Java recommendations, 3.1.1

Javadoc, 3.1.4

naming conventions, 3.1.5

SQL guidelines, 3.1.6

unit testing, 3.1.7

I

internationalization, 3.3.1

L

log entry format, 4.3

additional logging info, 4.3.3

example log entry, 4.3.4

fixed length header, 4.3.2

log entry description, 4.3.1

M

manager/technician framework, 10

new manager/technician, 10.1

manager class, 10.1.1

manager/technician reference, 10.2

P

Point-of-Service development standards, 4

preface, Preface

audience, Preface

R

retail domain, 15

domain object in tour code, 15.2

domain object reference, 15.3

code list map, 15.3.1

currency, 15.3.2

transaction, 15.3.3

new domain object, 15.1

run Point-of-Service, 2.2.3

S

screen design and user interface guidelines, 4.1

T

tour framework, 4.2, 12

aisles, 4.2.8

cargo, 4.2.13

choosing among sites, aisles, and signals, 4.2.10

foundation, 4.2.3

general tour guidelines, 4.2.2

managers and technicians, 4.2.6

roads, 4.2.7

shuttles, 4.2.12

sites, 4.2.5

tour architectural guidelines, 4.2.1

tour components, 12.1

aisles, 12.1.10

bus, 12.1.3

cargo, 12.1.4

service and service region, 12.1.2

sites, 12.1.5

system sites, 12.1.6

tour metaphor, 12.1.1

tours and services, 4.2.4

U

UI framework, 11

beans, 11.2

DataInputBean, 11.2.2

DialogBean, 11.2.4

field types, 11.2.5

NavigationButtonBean, 11.2.3

PromptAndResponseBean, 11.2.1

screens, 11.1

text bundles, 11.4

W

WeblogicApplication Server

install and configure, 2.1.3