Dear All, these are my porting results and impressions from 1.1.4pr1 to 1.1.4pr2 (2003.12.13).
1.1.4pr2 is really good, the internationalization of numbers and dates is a good idea. I haven't ever used interceptors but reading the docu the new version is better. These are my impressions porting from the previous to the actual version. --- DBFORMS-CONFIG-XML I encountered problems in dbforms-config.xml file, I had an error in my file (a table declared two times with the same name) and 1.1.4pr1 doesn't detect it, it seems that 1.1.4pr2 detects this problem... I think this is the problem of my previous post.... --- TEXTFIELDS AND NEW VALUES I read the releaseNotes about 1.1.4pr2 but I haven't understand how much is changed the textFields parsing & writing. I had some problems with "null" values in textFields, in labels, in dateFields. Where the previous version of dbforms prints "[No data]", in this new version I had an error. So I had to use the attribute "nullFieldValue" to put a text for the user. I don't know if there is a way to automatically put a comment like in the previous versione like "[No data]". ISSUE: I have noticed that in dateField there isn't a "nullFieldValue" attribute, I use dates with null values in my database to represent "actual active value" in historycal information.... now I have to use a textField insted dateField to manage this case. I discovered this after setting up a difficult debugging method in Linux with sysdeo (it runs only ONCE!!!)... anyone is debugging correctly under linux with eclipse??? When using navNewButton to insert new rows I had problems with null values; this values are calculated by postgres with triggers when the form passes a "null" value... with the attrib "nullFieldValue" now postgres receives another value and it isn't running well. So I have to delete this db:labels and change them with out.println(....). The "nullFieldValue" isn't a required attribute but if I skip it the JSP gives me a "Error:null" message when handling pageContext. --- INTERNATIONALIZATION The new way of printing number & date values with the current locale is good and useful. But in some cases I have to use a FIXED form indipendent from the locale settings.... so now I use a "pattern" attribute. OK. I don't know if there is a way to automatically set a default pattern instead of changing all "numeric" & "date" fields adding this new attribute. ---- Now I'm porting about 100 forms form 1.1.4pr1 to 1.1.4pr2, if you're interested I will post my impressions during this work... Regards Ivan ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
