From: Bill H. <bi...@lo...> - 2004-11-02 16:31:20
|
Hi Jon, Jon Austin wrote: >The output was simply > >embedded=true > >I'm wondering if JRUN is adding that, as the spring/hibernate combination >isn't behaving that way under tomcat. > > I can only assume your right. Hmm. The only solution that I can see is to check for that in the info object specifically. I would prefer for Proxool not to do that since it only takes JRUN to change that for it to break again. Another option is for you to not configure Proxool with XML but instead pass in the info object each time. Obviously, you'd want to create your own wrapper for that. That way, ProxoolDriver would always receive an identical info object and the pool wouldn't be redefined. It may seem like a simple fix to detect "embedded=true" and ignore it, but that means we are breaking a contract: someone passes a property to the driver and it is ignored. I've no idea why JRUN decides to send this property but it would be wrong for Proxool to make adjustments for it. If you wanted to, you could write your own JRUN JDBC driver that just took a URL like "jrun.foo", stripped out the "embedded=true" property and passed it on to the DriverManager as just "foo". That means you could configure Proxool how you liked. If none of these options seem appealing then get back to me, and we'll see what we can do. - Bill BTW, you would have received an answer on the proxool-user list too eventually. Most developers listen to both lists I think. |