cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrus Adamchik <and...@objectstyle.org>
Subject Re: Old web application needs a second database
Date Mon, 03 May 2010 12:28:46 GMT
Just to add some perspective (and hopefully not to confuse things  
further), our direction in Cayenne 3.1 is towards scenario #2, and  
getting rid of #1 completely. This way a user decides where his  
Cayenne stack (or multiple Cayenne stacks) is stored and how it is  
accessed.

Andrus


On May 3, 2010, at 3:19 PM, Andrus Adamchik wrote:

>
> On May 3, 2010, at 3:12 PM, Borut BolĨina wrote:
>
>> There will be cayenne.xml (with node A) and
>> my-cayenne.xml (with node A and B) on the classpath. Is that why?
>
> Yes.
>
>> I am not sure how to initialize.
>
> #1 is created implicitly when you call  
> DataContext.createDataContext(). That's the one returned from  
> Configuration.getSharedConfiguration().
>
> #2 you will have to create yourself and store somewhere. E.g. in a  
> ServletContext attribute.
>
> DefaultConfiguration conf = new DefaultConfiguration("my- 
> cayenne.xml");
> // store it for the app duration soemwhere
> ...
>
> // later when you need a new context:
> Configuration conf = .. // get it from ServletContext or from where  
> you put it
> return conf.getDomain().createDataContext();
>
> Andrus


Mime
View raw message