|
From: Michael A. <mic...@ze...> - 2004-03-27 14:51:44
|
OK, problem sorted. I was forgetting that SqlConfigService gets it's configuration from System.Properties, for exactly this reason, presumably. MikeA On Sat, 2004-03-27 at 02:50, Michael Ansley wrote: > Hmmm, I just tried using the SqlConfigService, and I got it started, and > then ran into a stack overflow, because: the SqlConfigService needs a > data source name (I'm using Jndi to store the DataSource object), but > it's trying to use itself to obtain the values to create the data > source. >=20 > Anybody out there actually using this kind of setup? And any idea how I > might force the SqlConfigService to use config files rather than falling > over itself? >=20 > Cheers... >=20 >=20 > MikeA >=20 |