File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Other Java Products and Servers and the fly likes Conversion from FAT client to Thin client - Check In/Out Document Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » Other Java Products and Servers
Bookmark "Conversion from FAT client to Thin client - Check In/Out Document" Watch "Conversion from FAT client to Thin client - Check In/Out Document" New topic

Conversion from FAT client to Thin client - Check In/Out Document

sparxgaurav gupta

Joined: Feb 05, 2010
Posts: 3
In one of our projects, we are converting an existing Thick Client Application (Swing Based) to a thin client solution using Spring MVC, JQuery and Websphere application Server. As a part of this conversion we plan to convert all existing functionalities AS IS using the new technology stack.

One of the existing functionalities has dependencies with the user’s desktop environment. Below points detail out the overall functionality of this feature:
- User can download an excel template workbook from the server along with a xml file containing data from the database.
- This excel file has pre-defined macros’ in it
- On open event of this excel, it reads the data XML file and populates the data into the Excel workbook
- The user can edit/modify the contents
- On Save or Close event of this workbook, the predefined macros convert the data from the Excel workbook into another output XML file which gets stored in a pre-defined location on the users desktop. On creation of this output XML file, a notification is sent to one of the ports on the desktop m/c.
- Another client side program unit keeps listening to this port and on notification reads & transmits this XML file to the server for updating the database

As a part of this conversion to thin client architecture, we want to achieve the same functionality AS IS
- Considering the various aspects and constraints in a web based environment, we are trying to seek for a possible or alternate solution towards this problem.
- We would like to have the new solution considering following aspects:
o Zero/minimalist changes to the users usability pattern that he is used to with the existing thick client solution
o Any potential security issues

Any suggestion/solution towards this problem will be of great help.

Thanks In Advance....

I agree. Here's the link:
subject: Conversion from FAT client to Thin client - Check In/Out Document
Similar Threads
Future of Browser versus Midlet Apps
Check In/Check Out Document Problem
Aspose.Total Product Family Q3 2010 Released
OpenOffice File Conversion formats
want to get more then 256 columns in XL using JXL API