This chapterlists the implementation specifics of Wireless Messaging API at package level.
The following general clarification is made towards JSR-205 client connection’s scope:
Symbian implementation supports sending of messages not only to the address specified when creating the client connection, but to other recipients as well. These recipients might be added after creating the client connection. This clarification applies to the following paragraph:
"If the application specifies a full destination
address that defines a recipient to the Connector, it
gets a MessageConnection that works in a “client” mode”.
This kind of Connection can only be used for sending
messages to the address specified when creating it."
(Chapter 1, Sending and receiving messages JSR-205 API specification)
The Series 40 implementation supports sending of SMS messages to the address specified when creating the client connection only, but sending of MMS to multiple addresses.
This class is supported as specified in JSR-205, with the following clarification for the following method:
open(String name, int mode,
Boolean timeouts)
This class is supported as specified in JSR-205.
This class is supported as specified in JSR-205, with the following exception for Symbian:
getTimestamp() always returns null in
the Symbian implementation.
In the Symbian implementation this class is supported as specified in JSR-205, with the following clarifications for the following methods:
newMessage(String
type)
newMessage(String address, String
type)
Parameter name | Parameter values |
|---|---|
| Can be one of the following:
|
send(Message)
In
the Symbian implementation this is implemented as a blocked call and returns
either after the Message has been sent or a 1-minute time-out occurred, in
which case an InterruptedIOException is thrown.
In the Series 40 implementation this is implemented as a blocked call and returns after the message has been sent. The Series 40 implementation does not use time-outs.
In
the Symbian implementation this class is supported as specified in JSR-205
with the following clarification: MessageListener MUST
not call receive() directly, as this will result in a
blocking operation. Instead, it can start a new thread which will receive
the message or call another method of the application (which is outside of
the listener) that will call receive() in a new thread.
In the Series 40 implementation this class is supported as specified in JSR-205.
This class is supported as specified by JSR-205, with the following clarifications for the following methods:
MessagePart(byte[] contents,
int offset, int length, java.lang.String mimeType, java.lang.String contentId,
java.lang.String contentLocation, java.lang.String enc)
MessagePart(byte[]
contents, java.lang.String mimeType, java.lang.String contentId, java.lang.String
contentLocation,java.lang.String enc)
MessagePart(java.io.InputStream
is, java.lang.String mimeType, java.lang.String contentId, java.lang.String
contentLocation, java.lang.String enc)
Parameter name | Parameter values | Clarification |
|---|---|---|
| The encoding scheme for the | The Symbian implementation allows the following String values for the encoding:
In
the Series 40 implementation, if |
| The Series 40 platform allows any character from 0x32 to 0x7E. |
This class is supported as specified by JSR-205, with the following method clarification:
setAddress(String
address)
Parameter name | Parameter values | Clarification |
|---|---|---|
| The JSR-205 states that address may be set to null | This call is interpreted as a blind call; the previously set addresses (if any) remain unmodified. |
All devices
support the bcc field for MultipartMessages.
This class is supported as specified in JSR-205 with no further clarifications.
This class is supported as specified in JSR-205.