As Marvin mentioned, most of our documentation/example code/XML probably only references a "dataSource" id object which is not valid if you've got three data sources. Its supported by Spring though (you can define an arbitrary number of data sources) but there are downstream affects. Each datasource may need its own Transaction Manager. If data sources are in the same transaction, it may mean a JTA transaction manager vs. the Spring platform one, etc.
On Tue, Sep 14, 2010 at 4:08 PM, Marvin Addison <[email protected]>wrote: > > Is it possible to specify three different datasources to handle > separately tickets, audit&stats and services? > > Sure, but it's an uncommon use case for which we don't have any > documentation. I believe many of the CAS Spring configuration files > expect a single datasource named dataSource, so you'll likely have to > touch several files to accomplish this. So it's possible but not > easy. It's not necessarily hard, either, but varies with your > familiarity with Spring configuration and CAS components. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
