Changes between releases

S60 platform

  • In S60 5th Edition

    No changes.

  • In S60 3rd Edition Feature Pack 2

    Added support for JSR-248, Mobile Software Architecture (MSA) requirements.

    • When sending a MessagePart with mime-type "text/plain" but without any value set for the encoding, the implementation will try to recognize the encoding and set it accordingly.

  • In S60 3rd Edition Feature Pack 1

    javax.microedition.securityservice.CMSMessageSignatureService only allows characters which can be found in the ASCII character set in caNames.

    • In S60 3rd edition FP1, non-ASCII characters in caNames cause IllegalArgumentException.

    • Previously, in S60 3rd edition, having non-ASCII characters in caNames caused certificates not to be found, and thus CMSMessageSignatureServiceException to be thrown with reason code CRYPTO_NO_CERTIFICATE.

  • In S60 3rd Edition

    This API was first supported in S60 3rd Edition. Earlier platform releases used an older version of Wireless Messaging API, JSR-120.

Series 40 platform

  • In Series 40 6th Edition

    Support for GSM cell broadcast service added.

  • In Series 40 5th Edition

    Added support for JSR-248, Mobile Software Architecture (MSA) requirements.

  • In Series 40 3rd Edition Feature Pack 1

    This API was first included in Series 40 3rd Edition FP 1. Earlier platform releases used an older version of Wireless Messaging API, JSR-120.

    Support for multimedia (MMS) files added.