[ http://jira.andromda.org/browse/SPRING-111?page=comments#action_12407 ] Safaa Hashim commented on SPRING-111: -------------------------------------
Any news if this issue will be addressed any time soon? Regards Safaa > Persist class/entity packages to multiple databases (data sources) > ------------------------------------------------------------------ > > Key: SPRING-111 > URL: http://jira.andromda.org/browse/SPRING-111 > Project: Spring Cartridge > Type: New Feature > Versions: 3.1RC1 > Environment: Any. > Reporter: Safaa Hashim > Assignee: Chad Brandon > > In real practice an application is partitioned into several business models > with the very likley potential that few of the different business objects are > persisted to totally different databases. This is important for business > reasons (Billing database, application database, transaction logging > database, business rules databases, multiple business domain databases, to > name few). > Currently AndroMDA can only persist to a single database which is defined in > the project.properties.xml as a datasource. > Potential Solution: > 1) allow the definition of multiple data-sources in the project > configuration, say ds1, ds2, etc. > 2) in the model provide a tag say <data-source> to associate a package of > entity classes with a data-source. The name of teh data-source would be the > value of the data-source attribute of the tag. > 3) In the generated code, generate multiple schema-create.sql and > schema-drop.sql scripts one for each data-source. > The above is only a conceptual outline of the proposed solution that I can > think of. > Thanks > Safaa ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
