>
>Any suggestions on what to do with the 3.1.1 tree? I'm going to try the
>"plasters over" patch for now...
The "plaster patch" on the 3.1.1 release seems to solve my immediate problem,
but I don't know what other problems might be lurking.
-- Sean
--
--
>"M. Sean Gilligan" <[EMAIL PROTECTED]> writes:
>
>I took a good look at the JndiDataSourceFactory and this patch just
>plasters over
What are the consequences of a patch that just "plasters over"?
>(there is also a good NPE chance in there)
I'm sorry, I'm not familiar with the acronym NPE, what
"M. Sean Gilligan" <[EMAIL PROTECTED]> writes:
I took a good look at the JndiDataSourceFactory and this patch just
plasters over (there is also a good NPE chance in there)
I reworked the config logic a bit, please try out, this should be
better now.
[]
> I plan on trying out a build tomorro
"M. Sean Gilligan" <[EMAIL PROTECTED]> schrieb am 29.12.2004
10:19:57:
> [...]
>
>
> I plan on trying out a build tomorrow. My CVS tree has the latest
> code, but I should probably build a patched version based on the
> TORQUE_3_1_1 tag if I want to put this into "production", right?
>
If yo
>"Wieger Uffink [Us Media]" <[EMAIL PROTECTED]> writes:
>
>>Ive recompiled torque source with a small patch in the
>>JndiDataSourceFactory and this solves the problem.
>
>Cool. Where is this patch? :-)
I'm not sure if he used the exact same patch as in this message:
http://nagoya.apache.org/eyebro