Mobile Task List with MIDP and JMS

Field staff using j2me enabled phones need to keep track on their tasks. A MIDLET shall allow CRUD on a simple taks list with this fields: - Entry date, Due date, Priority (High Medium Low), Description, Location, Status (New, Started, Completed, Cancelled), AssignedTo. Tasks need to be stored in the phone. There needs to be a matchin J2EE (Tomcat 5.x) application doing the same. The J2EE application also keeps a table with AssignedTo and their mobile phone #. Whenever a record is CRUD the two applications need to sync that one record using JMS. Preferable JORAM ([url removed, login to view] ) should be used, but open to suggestions. The JMS connection should be configurable: AutoConnect, periodic connect, transmit if connected otherwise.

## Deliverables

1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.

2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):

a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.

b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.

3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).

* * *This broadcast message was sent to all bidders on Thursday Dec 21, 2006 7:38:32 AM:

I have added explanations in a PDF document how we expect the application to behave. Please check it out in the bid documentation.

:-) stw

* * *This broadcast message was sent to all bidders on Wednesday Dec 27, 2006 8:09:08 AM:

Clarification:

1) We want a automatic continous update, not a user initiated one. (We have tons of that code). The JMS spec look like JMS provides that. Of course if there is a compelling alternative we are open to suggestions.

2) Security should be container managed since the J2EE container already is configured to use the enterprise directory to lookup users. The directory might change in the near future and we don't want to be forced to edit existing application code

3) On web applications one uses https to secure communication. We are not clear how communication can be secured using JMS.

## Platform

Server: Tomcat 5.x (Java 1.4.x compatible), not OS dependencies (must on Win/Linux) Client: J2ME Midlet e.g. Palm Treo, Nokia S60, Basic J2ME Phone.

Android Blackberry Database Administration Engineering iPhone MySQL PHP Software Architecture Software Testing SQL

Project ID: #3964435

About the project