First, *any* constructor can fail and throw an exception due to any number of factors -- including a JavaBean constructor.
Second, I did not write the beans in question. I'm simply seeking to maintain reasonable resiliency in their handling. My proposed change does that and is in better keeping with the intent of the spec than testing if the bean constructor actually succeeds at a given time.
Finally, though I strongly feel this patch is an overall improvement (and have received off-list mail to that effect), I will patch my own Tomcat as necessary if the Tomcat group is not flexible in this matter.
-- Jess Holle
Remy Maucherat wrote:
Jess Holle wrote:
I'm not arguing with the overall intent of your change. Rather I believe that calling the constructor during compilation is wasteful and improper as the environment *can* differ between compilation and runtime. Also, the fact that a failure to compile in this fashion generates a partial Java source means that once a compilation fails due to an environmental issue it will continue to fail even when the environment is corrected (e.g. when another server comes back up). That's certainly not appropriate.
At the heart of the problem is that you do not seem to know what a JavaBean is.
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
