> > If there are any other legitimate reasons - such as - you needed to
> > fix some bugs in the code that weren't being addressed in dbcp, then
> > you should just put the code in your source control system.
>
> If this was the problem, the right way to fix it would be to go and help
> out DB
Dan Armbrust wrote:
The only reasons he was given was that it was smaller (and we care
why?) and that it _might_ prevent a version conflict issue.
Size - don't care that much but as a side effect it isn't going to cause
any harm. Version conflicts, however, are a big issue. Many web apps
incl
"Dan Armbrust" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>> Did it occur to you that no-one would go to all this trouble unless
>> there
>> was a good reason for the re-factoring? Apparently not. If your tone had
>> been more reasonable I would have taken the time to explain
> Did it occur to you that no-one would go to all this trouble unless there
> was a good reason for the re-factoring? Apparently not. If your tone had
> been more reasonable I would have taken the time to explain the reasoning.
> Since it wasn't - STFW.
It was a sarcastic rant, because I was f
Dan Armbrust wrote:
So, my real question, is why the heck would anyone do this? What
possible purpose could all of this obfuscation serve? All you have
done is make debugging and trouble shooting 10 times more difficult
than it needs to be.
If you insist on refactoring the code for dubious rea
So, I have an issue with tomcat's database connection pool. Namely,
my connections keep getting closed, instead of reused.
I figured that the easiest way to figure out what was going wrong was
to put this in my debugger, so I could follow the close() call which
should release the db connection ba
