I am looking to try and build-up my learning on forms and flow (and templating!) by applying this to a simple interactive database app.
In the past, I used XSP and ESQL, along with a primitive "meta forms" XML file to generate a generic form *and* populate it with data, followed by styling with XSLT. Database add/update/delete were then handled by database actions in the sitemap (along with the corresponding table definition files). This approach may seem crude and simple but it worked and bugs (if any) were usually in a single XSP file and easy to track down. I am now wondering what combination of "new" options to adopt in order to replicate this approach in the simplest possible manner - I know there has been lots of discussion on persistence frameworks; DTO's, DAO's and business objects - but all this seems very much like over- kill just to tackle a few tables with a few users (in other words, a normal in-house, customised database app). I have seen flow samples with binding to beans and XML files, but nothing in terms of building up forms dynamically and then hooking then to a normal relational database to read/write data. Any pointers/steps/examples in this direction would be welcome! Thanks Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
