Thanks Joe, but that's my underlying problem. The datasource is based on the User session. The application is a single code-based application with multiple datasources serving different customers. A complex login happens when the user logs in to determine their source and authenticate them within that source, thereby establishing the datasource to utilize, so I can't hard-code any values in a configuration file, unless I have access to CF variables within it. Thanks,
Phil
From: Joe Rinehart <[EMAIL PROTECTED]>
Sent: Tuesday, December 20, 2005 12:58 PM
To: [email protected]
Subject: [coldspring-dev] Dynamic Datasource(stops lurking)
Hey Phillip,
I'd define a bean to hold datasource information, and wire it to the
CFC that needs it. That way, if datasource information need to
expand, you've got room to grow.
The XML would probably go a lot like this:
class="tld.domain.SomeBeanNeedingDatasource">
SomeDSN
SomeUsername
SomePassword
Cheers,
Joe
--
Get Glued!
The Model-Glue ColdFusion Framework
http://www.model-glue.com
