Address Management Bean

Author	David Hawes
Date	2008/09/02

Requirements

There exists no programmatic method to manage addresses and phone numbers in the Registry.

Ability to create addresses in the Registry for specific people
- Mail stop must be valid per the regular expression:
```
[\\p{Digit}]{4}
```
- State prov code must exist in the Registry
- Country code must exist in the Registry
- A person can only have one local address, one office address, and one home address
- If the address is unlisted, add a corresponding suppressed attribute
Ability to modify specific addresses in the Registry
- Mail stop, state prov codes, and country codes must be valid
- Add, remove suppressed attributes as appropriate
Ability to remove specific addresses from the Registry
- Associated phone numbers will be removed
- Suppressed attributes will be removed
Ability to create phone numbers in the Registry
- Phone numbers must be valid per the regular expression:
```
[\\p{Digit}]{10}
```
- If the phone number is unlisted, add a corresponding suppressed attribute
- For each type of address, a phone number can be of that type, or one of the following: mobile, pager, fax
Ability to modify phone numbers in the Registry
- Phone number must be valid
- Add, remove suppressed attributes as appropriate
Ability to remove phone numbers from the Registry
- Suppressed attributes will be removed
Ability to return a List of StateProv objects from the Registry
Ability to return a List of Country objects from the Registry

Must be implemented as a clustered stateless session bean.
Methods that modify the Registry must be sure to replicate the person whose information was updated.