And in mi opionion the best would be not to start the application if the config file could'nt be parsed! Or give some usefull hint somewhere.
The problem with the documentation is that - if you write the connection info first into your config file - the connection will be parsed correct and the error will happen on another place. We have a lot of problems with unparsable config files and error messages on other places. So my suggestion is to do a check in the dbforms tag if dbforms is initialized correct. If not then show an error page. Best solution is if we can show the reason for the wrong initialization.... What do you think? Regards Henner > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Im > Auftrag von Audun V. Nes > Gesendet: Mittwoch, 16. März 2005 19:42 > An: jdbforms-interest@lists.sourceforge.net > Betreff: Re: [dbforms] Manual Suggestion > > Hi > > Never a rule without an exception to confirm the rule :) I am > currently using DBForms with Oracle10g using the Oracle10g > JDBC driver, and I have plenty of varchar2 columns defined in > dbforms-config.xml - and it works :) > > best regards > Audun > > > On Wed, 16 Mar 2005 12:10:49 -0600, Bill Tribley > <[EMAIL PROTECTED]> wrote: > > Recently I had a devil of a time trying to figure out why my > > application was not using the default DbConnection. Turned > out that I > > used a non-ANSI sql column type, which caused the > DbForms-Config.xml > > parser to error out with a fatal exception. The application > continued > > to load, I had a valid context, but a stubborn exception > that was hard for me to find. > > > > I think that this paragraph would help, positioned in > section 5.6 at > > the end and in section 7.2.3 at the beginning. It may sound > > repetitive, and obvious, to the experienced. It gives some > important > > insight about how the application works. > > > > The paragraph: > > > > File DbForms-Config.xml is parsed when the servlet container is > > started, or when the web application is reloaded. If there are any > > errors in this file, the parser will abort with an > exception. However, > > the web application will continue to load. A valid context, without > > the database connections specified at the bottom of the > file, will be > > started. If everything else is OK, this will result in a "No > > DbConnection object configured with name 'null'" exception, > assuming > > that one default connection is specified. Besides the obvious xml > > syntax errors, it is an error to use a non-ANSI column type > > definition, for example the MySQL "enum" or the Oracle "varchar2". > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide Read honest > & candid > > reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start > reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > _______________________________________________ > > DbForms Mailing List > > > > http://www.wap-force.net/dbforms > > > > > -- > best regards > Audun > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from > real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > DbForms Mailing List > > http://www.wap-force.net/dbforms > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
