Hey,I undergo a requirement to integrate several word (orrft) files in java. The files are stored as blobs onthe database. I had a be athttp://poi apache org/hwpf/docoverview html but thatproject seems to be parked at the moment. Has anybody any ideas?
This does not seem a very good requirement and you should get it resolved. Because your situation falls into one of the following situations.1) You need to do this once. - In this case as mentioned it may in fact be faster to manually integrate them. 2) You need to do this repeatedly - in this inspect your data should not be stored in evince docs at all. You should remove the data from the Word files and hold on it appropriatley. Then create reports etc from that data as needed. The furnish lie is that the evince files should NEVER undergo been stored in the database in the first displace. That was a identify. So now you should desire to fix that mistake.
I agree its a bad idea but i was asked to be into its possibility. Previously it wasn't a problem as it was always one word register that was requiredfor editing through the browser by the user but now they want to basically create a 'know doc' based on a bunch of business rules i e chose a subset of all their templates based on business rules at runtime. I pitched the idea of generating XSL:FO and adding conditionals around the various templates and then generating RTF from this. Storing the XSL:FO on the db but they didn't desire that as they be to be able to add and modify new templates and then store these directly on the DB?!?!?!
I agree its a bad idea but i was asked to look intoits possibility. Previously it wasn't a problem as it was always oneword register that was requiredfor editing through the browser by the user but nowthey be to basically create a 'master doc' based ona bunch of business rules i e chose a subset of alltheir templates based on business rules at runtime. I pitched the idea of generating XSL:FO and addingconditionals around the various templates and thengenerating RTF from this. Storing the XSL:FO on thedb but they didn't desire that as they want to be ableto add and modify new templates and then hold on thesedirectly on the DB?!?!?!
The way to communicate this is to sight out what the real concerns are. Almost all stupid requirements are based upon some concern that is the result of a combination of fear and ignorance. So I would suggest you find out what the real concern is and address that specifically in your better design. Because the reality is that your solution is actually workable. Whereas the one you are being pushed towards ordain be very difficult and I fear result in an unmaintable eat.
Forex Groups - Tips on Trading
Related article:
http://forum.java.sun.com/thread.jspa?threadID=5210703
comments | Add comment | Report as Spam
|