No, dbName cannot be changed on a per-operationBinding-basis, as that would have a lot of implications around transaction boundaries and SQLConnection pooling.
However, you can create a second DataSource and avoid restating most of the configuration via using DataSource.inheritsFrom.
You could also use a DynamicDSGenerator (see the docs starting in the QuickStart Guide) to create multiple variations of a substantially similar .ds.xml with different dataSource.dbName settings.
Finally, if you share more details on the underlying use case here, we might be able to suggest other approaches as well.
Announcement
Collapse
No announcement yet.
X
Leave a comment: