Contactless Communication API - Oracle Software Delivery Cloud

More documents

Recommendations

Info

DiscoveryManagerDiscoveryManager — class in package javax.microedition.contactlesspublic class DiscoveryManager extends java.lang.ObjectMethod summaryvoidvoidvoidstatic DiscoveryManagerjava.lang.Stringstatic TargetType[]voidvoidvoidvoidaddNDEFRecordListener(javax.microedition.contactless.ndef.NDEFRecordListener listener,javax.microedition.contactless.ndef.NDEFRecordType recordType)addTargetListener(TargetListener listener,TargetTypetargetType)addTransactionListener(TransactionListener listener)getInstance()getProperty(java.lang.String name)getSupportedTargetTypes()removeNDEFRecordListener(javax.microedition.contactless.ndef.NDEFRecordListener listener,javax.microedition.contactless.ndef.NDEFRecordType recordType)removeTargetListener(TargetListener listener,TargetTypetargetType)removeTransactionListener(TransactionListener listener)setProperty(java.lang.String name,java.lang.String value)InheritanceDescriptionjava.lang.Object → DiscoveryManagerMethods inherited from class java.lang.Objectclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitThe DiscoveryManager class offers the mechanism to discover targets for contactless communication. It is the startingpoint for the application using the Contactless Communication API . This class also manages the different listeners in thisAPI.This class also provides a method to query contactless targets supported by the API implementation. MethodgetSupportedTargetTypes returns the list of supported contactless targets. All the targets that can be accessed throughthis API are specified in the TargetType class.TargetListener is used to request a notification for a specific contactless TargetType the application is interested in.NDEFRecordListener provides a notification about specific NDEF record type that is in the read from the NFC Forum complianttag.Inside a Java virtual machine, there must be at most one TargetListener for each TargetType . The restriction forone TargetListener is needed, because the RFID hardware is able to handle only one connection to the physical targetat a time. The registration of TargetListener should fail, if there is an existing listener in other virtual machines or inthe native platform. The addTargetListener method throws an exception, if there is an existing listener defined. Theexisting listener may be a native application.11
Package javax.microedition.contactlessDiscoveryManagerThe API implementation must restrict the number of simultaneous listeners set for one NDEF record type. The reason forthe restriction may be usability or hardware restrictions. The addNDEFRecordListener method throws an exception if themaximum number of registered listeners for an NDEF record type is exceeded. On the MIDP 2.x platform the PushRegistryentry for an NDEF record type in a MIDlet that is not executing increases the number of registered listeners by one. Moreinformation about PushRegistry in the Appendix B: Launching applications with MIDP 2.x PushRegistry .An application can get information about NDEF formatted data on a NDEF tag target through both TargetListener andNDEFRecordListener . If the application wants to write data to the tag, it must register TargetListener . If theapplication is only interested in the data in specified record type on the tag, it should register NDEFRecordListenerfor that record type. The data provided in the NDEFRecordListener notification is read-only and the application hasno access to the target after receiving this notification. One application may set both of these listeners at the same time.In this case the application has to be aware that the notifications may arrive almost simultaneously and to design theapplication accordingly. Applications should not register listeners for targets or for NDEF records it is not interested in.The following diagram depicts the relationships of the two listeners that the application can register for NDEF_TAG target.Diagram also specifies the order in which the notifications must be sent.12
Page 1 and 2: Contactless Communication APIJSR 25
Page 3 and 4: 2.2 You shall not be allowed to rem
Page 5 and 6: PrefaceThis specification was produ
Page 7 and 8: OverviewIntroductionGoalsThis speci
Page 9 and 10: Related documentation[CDC] Connecte
Page 11 and 12: API Reference
Page 13 and 14: Package javax.microedition.contactl
Page 15: ContactlessExceptionInheritanceCont
Page 23 and 24: TagConnectionInheritanceTagConnecti
Page 25 and 26: TargetPropertiesTargetProperties
Page 33 and 34: NDEFMessageNDEFMessage — class in
Page 43 and 44: NDEFRecordTypeNDEFRecordType — cl
Page 47 and 48: NDEFTagConnectionNDEFTagConnection
Page 51 and 52: PlainTagConnectionPlainTagConnectio
Page 59 and 60: ImagePropertiesImageProperties —
Page 65 and 66: SymbologyManagerSymbologyManager
Page 67 and 68:
VisualTagCodingExceptionInheritance
Page 69 and 70:
Package javax.microedition.contactl
Page 71 and 72:
Appendix A. SecurityThis appendix d
Page 73 and 74:
}* Creates a new ContactlessPermiss
Page 75 and 76:
}/*** Returns the hash code value f
Page 77 and 78:
import javax.microedition.io.GCFPer
Page 79 and 80:
* @author Nokia Corporation* @versi
Page 81 and 82:
Appendix B. Launching applications
Page 83 and 84:
Appendix C. Unique identifiers of t
Page 85 and 86:
Appendix E. Examples of RFID commun
Page 87 and 88:
}if (target != null) {// do the com
Page 89 and 90:
equals, 40exchangeData, 50externalR
show all

Contactless Communication API - Oracle Software Delivery Cloud

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?