Difference between revisions of "Org.eclipse.higgins.icard.registry"

Revision as of 19:19, 26 January 2007

Overview

• Manages the user's set of I-Cards
• Each I-Card is instantiated and managed by an I-Card Provider
• Each I-Card implements the I-Card Interfaces
• Status: first code in M0.6
• Language: Java
• Packaging:
  • Suse and Red Hat (Gnome): {GCJ Binaries: {x86,?} * {Bindings: C, C++} * {RPM, Debian}
  • OSX: {GCJ Binaries: {x86,?} * {Bindings: C, C++} * TBD
  • Windows: {GCJ Binaries: {x86,?} * {Bindings: C, C++} * MSI
  • Java: OSGI bundle
  • Java: WAR
• Client Deployment:
  • Part of the {ISS Client UI, I-Card Selector Service, I-Card Registry, Token Service} bundle.
• Server Deployment:
  • JSP on Tomcat or OSGI app server

Service

• The I-Card Registry is a thin layer over a set of I-Card Providers

• The I-Card Registry API has two parts:
  • An API to add an i-card, remove and i-card and iterators to walk through the list of i-cards.
  • A set of interfaces that are implemented by each I-Card Provider

I-Card Registry API

Iterable<CardRef> getCards()

createCard()

deleteCard()

importCard()

exportCard()

See Also

• I-Card Provider
• I-Card Selector Service
• Core Components