DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18347>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18347 [VELTOOLS][PATCH] Avoid dummy tools creation in ViewToolInfo constructor [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-04-01 21:02 ------- yeah, we could use reflection to test for the constructor, but if i want to get picky, i could say that we still don't really know if the object can be constructed. exceptions might still be thrown when actually invoking the constructor. it may be just a matter of whether you want to get errors at startup or later on. personally, i think it's best to give things an opportunity to break as early as possible. if not at compile, then at runtime setup. as for funky things like a MailTool or DatabaseTool, if they are application-scoped, then, like all application-scoped tools, they will be created during runtime setup anyway (see ServletToolboxManager.addTool()). if they are being placed in session or request scope, then it's probably bad practice to do much "connecting" or other heavy-lifting in the constructor period. IMHO, a lazy approach where tool setup happens only when needed/used is best in those situations. otherwise you might be taking some needless performance hits. i think at this point, i'm going to mark the bug invalid, but please feel free to reopen it if you want to discuss it further. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
