Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (herse.apache.org: domain of rickcr@gmail.com designates
 66.249.92.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=CFyhNZZPe5bXmkBS/UwNUgITwdjxGRZHUcOrDxqgc7/i9vbuuS8xZ9dPiaYTx2ruivq+cNSr9mPqRQhwMdSMsPUlQYw5mQJ2v3fqrNwyrg/I7kkydxIB/xJzwfHd3C0w8FDPmcsRS84bFJlYhB1kX99D3DfOoBYd9XxCbCB2T7o=
Message-ID: <583d4dff0612010831p5a11f937m9b5d6d3493c3707d@mail.gmail.com>
Date: Fri, 1 Dec 2006 11:31:16 -0500
From: "Rick Reumann" <rickcr@gmail.com>
To: user-java@ibatis.apache.org
Subject: Questions on allowing users to switch to a different datasource
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2750_2325888.1164990676169"

------=_Part_2750_2325888.1164990676169
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I'm a slacker and not using Spring to create any iBATIS daos.

In my existing application I'd like to allow the user to be able to to
switch between going against a dev or test/qa db.

What I was thinking of doing is...

1) app start up (or lazy on first base dao call), I'd populate two
SqlMapClient objects (one dev, one test). This creates a bit of problem,
though, since I've been building the SqlMapClient object as
SqlMapClientBuilder.buildSqlMapClient(reader); -- but the reader reads from
the sqlMapConfig file which points to my datasource. I don't mind
duplicating that config file and have each point to the datasource I want,
but it seems there must be a better way to set it up since each file would
end up with all the duplicate sql map definitions, etc.

2) Users then get their own dao in Session which has a handle to either the
dev or qa SqlMapClient. If the user switches to another datasource (picks
from a drop down in the front end), the sqlMapClient in their dao instance
will point to the new one they chose.

I haven't figured out how I want to handle the service layer, but that part
won't be bad.

I'm more concerned at this point as the approaches others have taken.

Thanks.

------=_Part_2750_2325888.1164990676169
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I'm a slacker and not using Spring to create any iBATIS daos. <br><br>In my existing application I'd like to allow the user to be able to to switch between going against a dev or test/qa db.<br><br>What I was thinking of doing is...
<br><br>1) app start up (or lazy on first base dao call), I'd populate two SqlMapClient objects (one dev, one test). This creates a bit of problem, though, since I've been building the SqlMapClient object as SqlMapClientBuilder.buildSqlMapClient
(reader); -- but the reader reads from the sqlMapConfig file which points to my datasource. I don't mind duplicating that config file and have each point to the datasource I want, but it seems there must be a better way to set it up since each file would end up with all the duplicate sql map definitions, etc.
<br><br>2) Users then get their own dao in Session which has a handle to either the dev or qa SqlMapClient. If the user switches to another datasource (picks from a drop down in the front end), the sqlMapClient in their dao instance will point to the new one they chose.
<br><br>I haven't figured out how I want to handle the service layer, but that part won't be bad.<br><br>I'm more concerned at this point as the approaches others have taken.<br><br>Thanks.<br>

------=_Part_2750_2325888.1164990676169--