Search for project
More than 2000 projects issued through our platform and this
amount increases very fast.
Simple J2EE App (ID:2635)
| Project Creator: |
zaebos
FC Member For 6581 Days
Credits 20 Completed Proj. Num. 0 / 1 Total payment USD 80.00 Avg Daily Online 0.00 h (From 21/5/2007) Available on MSN/Skype Yes Last Login 7/12/2007 Peers Rating 0.00% 
|
|---|---|
| Budget: | Less than 250 |
| Created: | 7/3/2007 7:16:12 AM EST |
| Bidding Ends: | 7/10/2007 7:16:12 AM EST ( Expired ) |
| Development Cycle: | 1 Days |
| Bid Count: | 5
|
| Average Bid: | 120.00 |
| Project Description:
I need a very simple j2ee app(command line client that stores and displayes records) converted into a j2ee app using jsp and servlets accesible via a webpage. It should only be a few hours work as a lot has been done already, and I will pay well. Newly added descriptions: Potential Candidates: There are a few extra conditions on my project, that if you are fine with I would be happy to hire you, I have listed them out here. make a web client instead of a command-line client. You may choose to use any mix of JSPs and servlets. Javascript may be used, but is not required Make appropriate use of transactions (J2EE transactions - use of @ejb.transaction etc). [To avoid confusion, for storing and deleting information, you need to use transaction to refer to a J2EE transaction.] Support multiple users. All users are authenticated users. All authenticated users should be allowed to view list reports. The enterer role should be allowed to add the information of new customers and books. The admin role should be allowed to borrow and return a book. Typically a user who was granted the admin role would also be granted all the other roles, so you might expect to see a line in roles.properties that looked like: dougt=admin,enterer Since the web client will run in the same JVM as the EJBs there is no longer any *need* to use a session facade. However, you may still find it useful to use one. The choice is yours. The code should already perfrom the following functionality, if it does not it must be checked/implemented: 1. Keeping records of new customers 2. Keeping records of new books 3. Keeping records of borrowed books 4. Keeping records of books returned The information for a particular entity needed to be stored in the database is as follows: Entity Attributes Format Customer custID String custName String Book callNo String Title String Borrowing custID String callNo String borDate Date Return callID String retDate Date For recording customers and books, a user of the LMIS will present their relevant information. The system will automatically check for duplication of entry. The duplication is to be checked using custID and callNo for customers and books, respectively. If a duplicate entry exists, system should produce message for duplicate entry. For borrowing of a book by a particular customer, its availability is to be checked first. If the book has already been borrowed by a customer or not available for other reasons, the system will not issue that book and will produce an indicative message. A successful borrowing will add the book into the borrowing list using the attributes described in the above table and display a message that borrowing has been successful. Regards, Jason Evans |
|
| Job Type | JSP |
| Attached Files: | 20070703071601.zip |
