You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the public document for SEEK 3.1 seems to indicate its compliancy with
OpenMobile 2.04 at
http://seek-for-android.googlecode.com/svn/trunk/doc/index.html
with the following wording:
public class SEService extends Object
The SEService realises the communication to available Secure Elements on the
device. This is the entry point of this API. It is used to connect to the
infrastructure and get access to a list of Secure Element Readers.
See Also:SIMalliance Open Mobile API v2.04
However, it is missing the getVersion API support mentioned in OM 2.04 at the
following section:
6.4.5
Method: String getVersion()
Returns the version of the Open Mobile API specification this implementation is
based
on.
Return value:
String containing the Open Mobile API version (e.g. "2.04").
SEEK should consider implementing this function as a "static" method.
The reason this should be a static method instead of a member method is because
this is an information-al only API that should not require access/specific
instance of any class of OpenMobile.
Original issue reported on code.google.com by [email protected] on 30 Jan 2014 at 10:33
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 30 Jan 2014 at 10:33The text was updated successfully, but these errors were encountered: