ServerRuntime is the "root" object of Cayenne. So there's no other place to store it as far as Cayenne is concerned and this is by design.
The whole point of the recent Cayenne evolution was to make Cayenne 100% embeddable and manageable in any environment. Introducing a static singleton in Cayenne (not in your code) is contrary to that goal. Andrus On Feb 28, 2013, at 9:10 PM, Michael Gentry <[email protected]> wrote: > Hi Andrus, > > I thought about using the ServletContext, but that felt a bit "dirty", so > I'll probably create a singleton to store the runtime. I just thought > maybe there was already a place in 3.1 that I didn't see for the most > common case where you only have one runtime to save. > > Thanks, > > mrg > > > On Thu, Feb 28, 2013 at 12:45 PM, Andrus Adamchik > <[email protected]>wrote: > >> Either your own singleton, or ServletContext. ServletContext is >> essentially a designated place for app-scoped objects in a webapp. >> >> Of course if you have Tapestry or Spring (that are themselves internally >> attached to ServletContext), you can use those for ServerRuntime access via >> injection. >> >> Andrus >> >> On Feb 28, 2013, at 5:43 PM, Michael Gentry <[email protected]> wrote: >> >>> Is there an existing place (class) in 3.1 to stuff a ServerRuntime >> instance >>> for global use or is it expected that you'll create a separate class to >>> hold a static instance variable of ServerRuntime? >>> >>> Thanks, >>> >>> mrg >> >>
