OpenCard Framework 1.2 Programmer's Guide - OpenSCDP

Recommendations

Info

card, you’ll have to enter the password password when this method is invoked. For user convenience, we finally print what has been written to the file: // write the data to the file facs.write(file.getPath(), 0, data); System.out.println(entry); Note that only one method invocation was required to write the data to the file. The rest has been done to prepare the data, which has nothing to do with OCF or smart cards. Here is the complete listing of the second sample application: import opencard.core.service.SmartCard; import opencard.core.service.CardRequest; import opencard.opt.iso.fs.FileAccessCardService; import opencard.opt.iso.fs.CardFile; public class InitFile { public static void main(String[] args) { System.out.println("initializing file..."); try { SmartCard.start(); // wait for a smartcard with file access support CardRequest cr = new CardRequest(CardRequest.NEWCARD, null, FileAccessCardService.class); SmartCard sc = SmartCard.waitForCard(cr); FileAccessCardService facs = (FileAccessCardService) sc.getCardService(FileAccessCardService.class, true); CardFile root = new CardFile(facs); CardFile file = new CardFile(root, ":c009"); String entry = args[0].replace(':', '\n'); byte[] bytes = entry.getBytes(); int length = bytes.length; byte[] data = new byte [file.getLength()]; if (data.length < length) length = data.length; System.arraycopy(bytes, 0, data, 0, length); // write the data to the file facs.write(file.getPath(), 0, data); System.out.println(entry); } catch OpenCard Exceptions { e.printStackTrace(System.err); } finally { // even in case of an error... try { SmartCard.shutdown(); } catch OpenCard Exceptions { e.printStackTrace(System.err); } } System.exit(0); } } 10 OpenCard Framework 1.2 Programmer’s Guide
Chapter 3. OCF architectural concepts Architecture overview This chapter provides an overview of the OPENCARD architecture. We’ll briefly explain the key concepts of the OPENCARD FRAMEWORK and put them in relation. We’ll provide enough background to show how OCF brings together the various technology providers of the smart card industry, the application developers, the card terminal manufacturers, the card or card operating system manufacturers, and the card issuers. Finally, we’ll introduce those concepts that are most relevant for application developers. We can divide the OPENCARD FRAMEWORK into two main parts: The CardTerminal layer and the CardService layer (see also Figure 1). Figure 1. Main parts of the OPENCARD FRAMEWORK architecture. The CardTerminal layer contains classes and interfaces that allow you, the application developer, to access card terminals and their slots. Using these classes you can, for example, find out whether a smart card is inserted in a card terminal. The CardService layer defines the abstract CardService class: OCF represents smart card functions through card services. Each card service defines a particular (high-level) API that you can use to access some particular smart card function; for example, the file access card service gives you access to the file system of a smart card. Both of OCF’s layers — CardTerminal and CardService — are designed using the abstract factory pattern and the singleton pattern (as described in Design Patterns — Elements of Reusable Object-Oriented Software). The objects dealing with the 11
Page 1: OpenCard Framework 1.2 Programmer
Page 4 and 5: OpenCard Framework 1.2 — Programm
Page 6 and 7: iv OpenCard Framework 1.2 Programme
Page 8 and 9: Defining your own interface . . . .
Page 10 and 11: viii OpenCard Framework 1.2 Program
Page 12 and 13: Where you can get OpenCard Framewor
Page 14 and 15: applications across a wide range of
Page 16 and 17: 4 OpenCard Framework 1.2 Programmer
Page 18 and 19: import opencard.opt.iso.fs.CardFile
Page 20 and 21: public class ReadFile { public stat
Page 24 and 25: The CardTerminal layer manufacturer
Page 26 and 27: The CardService layer Figure 3. The
Page 28 and 29: 16 OpenCard Framework 1.2 Programme
Page 30 and 31: The utility class opencard.core.uti
Page 32 and 33: Initializing the OpenCard Framework
Page 36 and 37: Working with files Files in the sma
Page 38 and 39: specific card. We have already expl
Page 42 and 43: To lock a terminal you can use the
Page 44 and 45: } catch OpenCard Exceptions { // ex
Page 46 and 47: The counterpart to the register met
Page 48 and 49: Referencing by DF name: DFs can ref
Page 52 and 53: Using the trace utility Provided a
Page 56 and 57: The Java Plug-In This is basically
Page 58 and 59: v Generate a certificate: javakey -
Page 60 and 61: Native Browser support By native br
Page 64 and 65: The Constructor: First, you should
Page 66 and 67: (known as the ″case four″ comma
Page 68 and 69: Now you have a overview of the impl
Page 70 and 71: card removal events you should impl
Page 72 and 73:
60 OpenCard Framework 1.2 Programme
Page 74 and 75:
After OCF has been started, the wai
Page 76 and 77:
CardServiceInterface The methods fo
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
determine the card type the CardSer
Page 84 and 85:
BasicAppletCardService The class Ba
Page 86 and 87:
} } // Initialize the framework Sma
Page 88 and 89:
Acknowledgements 76 OpenCard Framew
Page 90 and 91:
CardServiceRegistry. A system-wide
Page 92 and 93:
smart card on a per-message basis.
Page 94:
show all

OpenCard Framework 1.2 Programmer's Guide - OpenSCDP

Create successful ePaper yourself

Delete template?

Save as template?