[[middleware:devel:ed:name-manage]]
 
Trace: » deprov-email » prov-group-email » name-arbiter » middleware » entitlement-scheduler » dat » usage » pid-scheduler » registry-core » name-manage
Table of Contents

Name Management Bean

Author David Hawes
Date 2008/09/02

Requirements

Problem Statements

  • There exists no programmatic method to manage names in the Registry.

Functional Requirements

  1. Ability to create a name in the Registry for a person
    • Names are of the types: preferred, non-preferred, alumni
    • Name must be valid per the regular expression: 
      [\\p{Alpha}][ \\p{Alpha}'-.]*
      • Note: this will be changed from p{Alpha} to p{L} to include international characters for the Banner upgrade
  2. Ability to modify a name in the Registry for a person
    • Names must be valid
  3. Ability to remove a name in the Registry for a person

Nonfunctional Requirements

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

Useful links

Comments

 
middleware/devel/ed/name-manage.txt · Last modified: 2009/10/07 17:17 (external edit)
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki