My path solves this problem by
adding an interceptor which, on insert/update, takes the file metadata and stores it into some field specified.

This way, the file metadata is preserved, but the BLOB is not polluted by some serialized java wrapper object and can be accessed by any other app.

My question is:

- if so, which one should be default (new or old)?

I say the default should be the new way. We maintain a section on upgrading (Compatibility notes: --in the Installation section) where we can put how to keep the old behavior if desired. This way, all new users will be using the best way. For previous users, adding a line to dbforms-config.xml to retain the old behavior will be trivial IMHO.
--
Shawn


Happily using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/


------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ DbForms Mailing List

http://www.wap-force.net/dbforms

Reply via email to