entifier myCassetteIdentifier = new CassetteIdentifier("purchase", 1, 1); private static final CassetteIdentifier[] dependencyIdentifiers = null; public CassetteControl() {}/* Cassete abstract method redefinitions */ protected CassetteIdentifier getCurrentVersionIdentifier() { return myCassetteIdentifier; } protected CassetteIdentifier[] getDependencyIdentifiers() { return dependencyIdentifiers; } protected void install() { registerOperation( PurchaseOperation.OPERATION_NAME, "com.sun.commerce.purchase.PurchaseOperation"); }/* These methods are not implemented yet. */ protected void init() { } protected void shutdown() { } protected URL[] getJCMForLatestVersion() { return null; } protected Date getExpirationDate() { return null; } protected boolean doUpdate(Date lastUpdate) { return false;} protected void uninstall() { }}Create the Java Commerce Message for the Purchase Operation Every operation requires an associated Java Commerce Message (JCM). A JCM is an electronic message sent from the web server to the client JCC framework. There are many ways to structure a JCM transaction. One scenario for a purchase transaction initiated in an applet could be as follows: A shopper makes a selection that triggers the electronic purchase operation. The web server applet then queries the shopper for payment and other relevant information, plugs that information into a JCM template, and sends the JCM to the JCC framework installed on the initiating client's system. The JCM contains a body of name=value pairs that describe the transaction. When the JCC framework finds the operation=purchase line in the JCM, it searches for the purchase operation cassette specified in the CassetteIdentifier method in the CassetteControl class. In this example, the purchase cassette is purchase_1.1. The JCC framework then passes the JCM to that operation Bean, which in turn parses the JCM. Here is...
