Home >> All

•	mobile.bearer.* (6)	•	mobile.bearer.http.* (6)	•	mobile.jmsapi.* (28)
•	mobile.jndi.* (3)	•	mobile.protocol.* (7)	•	mobile.util.* (2)
•	mobile.util.synchronization.* (2)

• mobile: Javadoc index of package mobile.


Package Samples:

• mobile.bearer.http
• mobile.jmsapi
• mobile.jndi
• mobile.protocol
• mobile.util.synchronization

Classes:

• MobileRequestManager: This class implements a thread which manages requests sent from the mobile to the proxy and replies comming from the proxy. Each time a JMS or JNDI method is called in the jmsapi layer, a request is generated. It is than added to the request queue, where it waits to be sent to the proxy server. If the request needs to be answered, the calling thread waits until a reply arrives. When the proxy server sends the reply, it is added to a reply queue and all the waiting threads are woken up. The thread waiting for this reply deletes it from the queue. The main thread checks in a loop if there are requests ...
• HttpConnectionExample: This file is not used in the project, its only source of good concepts An example MIDlet to fetch a page using an HttpConnection. Refer to the startApp, pauseApp, and destroyApp methods so see how it handles each requested transition. Note: if you run this inside POSE using a multi-homed PC (with more than one network connections), POSE doesn't know how to resolve host names not connected to the first network card. To solve this, add a line like this in your c:/WINNT/system32/drivers/etc/hosts file: 204.71.202.160 www.yahoo.com
• Frame: The Frame class is an abstract class implementing a message which is sent between the library and the proxy server. The message concerns a JMS action such as creation of a new JMS object on the mobile device, a call of a JMS method on this object or a JNDI action, such as a lookup of a JMS administered object.
• Protocol: This is set of constants used to determine kind of message. While message body is "serialized" into bytes stream, there must be a mechanism to determine how to understand what is the message.
• Request: This class provides implementation of message sent to the proxy server. This message represents an action such as a call of a JMS or JNDI method.
• NoDataException: Description: Exception thrown by TalkingWithProxy when proxy answers with no data. Copyright: Copyright (c) 2003 Company: jms4j2me
• Library: This class provides access to the MobileRequestManager and TalkingWithProxy objects and ensures that both objects exist as singletons.
• NoConnectionException: This Exception is thrown by HttpConnection when proxy is unrichable Copyright: Copyright (c) 2003 Company: jms4j2me
• FrameQueue: The FrameQueue class implements a queue of Frame objects. It provides the queue interface, which is not available in the MIDP.
• Reply: This class provides implementation of a reply message sent by the proxy server in reply to a request from a mobile device.
• Test1: Description: Tests serialization of requests in mobile.protocol and their construction i proxy.protocol
• BinarySemaphore: Title: Instant-Messenger Description: Copyright: Copyright (c) 2003 Company:
• TalkingWithProxy: The lowest level of communication, Makes connection with proxy using HTTP protocol.
• MesgPropTest: Title: Description: Copyright: Copyright (c) 2003 Company:
• StringIterator: Title: Description: Copyright: Copyright (c) 2003 Company:
• rmsTest: A test case, testing request serializing for the needs of storing them in the record store
• Context: class representing java.naming.Context implementing only method lookup, however
• TopicSession: class representinf a session of a connection with JMS provider in Pub-Sub mode
• QueueConnection: class representing JMS Connection in Queue mode with the priovider
• TopicConnection: class representing connection with JMS provider in Pub-Sub mode
• TalkingWithProxyTester: A TalkingWithProxy testing tool. Invokes test cases on kvm.
• Id_class: This is parent class for all classes in the jmsapi package.
• LookupMid: A TalkingWithProxy testing tool. Invokes test cases on kvm.
• Session: class representing session of connection with JMS provider
• Destination: class representing source or destination of JMS messages

Home | Contact Us | Privacy Policy | Terms of Service