DevForce Community Forum : Set data source extension at runtime?

Set data source extension at runtime? : Thanks for the reply Kimj,Changing...

Tue, 18 Aug 2009 12:51:20 -700

Author: mtx_kguil
Subject: 1427
Posted: 18-Aug-2009 at 12:51pm

Thanks for the reply Kimj,

Changing the name attributes of the edmKeys to "Default_Local" and "Default_Remote" (Instead of just "Local" and "Remote") did the trick!

Set data source extension at runtime? : Do you also have EdmKeys defined...

Tue, 18 Aug 2009 11:29:23 -700

Author: kimj
Subject: 1427
Posted: 18-Aug-2009 at 11:29am

Do you also have EdmKeys defined for each, in both the client app.config and the web.config? The web.config needs the two EdmKeys, say "Default_Local" and "Default_Remote", so that it can obtain the correct database connection information; while the client app.config needs the two keys - with the same key names as used in the web.config - to both identify the data source and also the correct EntityServer service.

Set data source extension at runtime? : Hello,I am currently working...

Mon, 17 Aug 2009 13:46:25 -700

Author: mtx_kguil
Subject: 1427
Posted: 17-Aug-2009 at 1:46pm

Hello,

I am currently working on a application that requires access to two separate but identically structured databases.

From what I got out of the documentation it seems easy enough, just define the data source extension in the web.config, refer to it when creating the EntityManager, and add the appropriate .svc file.

cl = new DomainModelEntityManager(true, "Local");
cr = new DomainModelEntityManager(true, "Remote");

However, when I do this it always seems to use whichever data source extension that is defined in the Object Mapper.

Anyone have any suggestions?

Thanks,

Edited by mtx_kguil - 17-Aug-2009 at 1:49pm