- Support for full JMS 1.1 API
with following exceptions:
- Float/Double message properties are not allowed
(floats/doubles are not supported on midp devices).
- Multiple jms connections from one client application
are buggy, this will change soon.
- Currently also there is no support for secured
Connections. User name and password provided to
ConnectionFactory is ignored. This will be corrected
together with multiple connections support.
- Object messages are not implemented (midp does not
support object serialization).
- Message sending has a little bit different semantics.
In normal JMS messages are sent synchronously, and
once sending finishes message is sent to JMS queue or
topic. We have choosen asynchronous message sending
model due to transient nature of mobile devices
network connections. Messages are stored, and sent as
soon as the connection is available (possibly
immediately). This means that when the send method
returns, message might still be on the mobile
device. Additional, beyond JMS, api will be provided
to check if message has left to JMS.
- All above applies also to all other JMS operations.
The remote commands (e.g. create new session) are
processed the same way as messages. This also means
that exceptions thrown by JMS are delivered
asynchronously. Unfortunately it means that succesfull
execution of JMS method on JMSME doesn't mean it will
succeed on JMS server. That's why ExceptionListener
should always be registered.
- ConnectionMetaData is not supported.
- Supported Devices: below is the list of mobile
devices on which jmsme has been tested, and is supposed to
work. Unless noted otherwise, tests were run on emulators. We will
try to verify test results on real devices, and update this
list. If you successfully launch jmsme on devices not mentioned
here, please let us know.
- Palm handhelds:
Tested on POSE emulator with SUN's MIDP
implementation installed.
HTTP communication works fine.
UDP communication not supported by this MIDP implementation.
- Siemens Cellular phones
| S55, M55 |
Poor UDP implementation. Does not allow
simultanous sending and receiveng over one
socket.
HTTP works fine. (on emulator)
|
- Motorola - Tested on Motorola iDEN emulator. Works fine
if you set enough memory :)
HTTP works fine.
UDP works fine.
- Wireless Toolkit Emulator (wtk):
HTTP works fine.
UDP works fine.
|
|
