For the benefit of those planning to upgrade to dbforms 2.x here are changes
I have had to deal with (though I haven't finished the upgrade yet):
i) 2.x break backwards compatibility with 1.1.3 on a number of features:
a) Interceptors have to be changed to conform to 2.x format
b) Some tags don't behave the same way. I don't know if some of these were
intentionally programmed this way. e.g. <db:radio fieldName="ref"
value="0" /> won't work in 2.x, you have to use <db:radio fieldName="ref"
defaultValue="0" />
ii) The workflow also appears to have changed e.g. when I delete a record in
1.1.3 dbforms moves to the next record while in 2.x it moves to the first
records.
iii) Some new features/enhancements are good but could change the way the
application works. e.g. the update button does nothing if no data has
changed. This is a wonderful enhancement but I wish there was a way to make
this behaviour optional. For instance, sometimes I would like to call the
postUpdate() interceptor whether or not data has changed without resorting
additional JSP manoeuvres.
There could be many more changes, I have just touched on what I have seen so
far. To make upgrading easier can others post their experience.
JM
----------
DISCLAIMER: This email and any files transmitted with it are confidential and intended
solely for the use of the recipient. Any disclosure, copying or distribution of all or
part of the information contained herein to or by third parties is prohibited and may
be unlawful.
In any event the contents herein is without prejudice.
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms
