> On Mar 13, 2024, at 7:09 AM, Shawn McKinney <[email protected]> wrote: > > The problem, the xml data corresponding which each additional tenant would > have to separate, because that is how the APIs work currently. > > e.g. > > ``` > mvn install -Dload.file=acme.xml -Dtenant=acme > mvn install -Dload.file=foo.xml -Dtenant=foo > mvn install -Dload.file=bar.xml -Dtenant=bar > ``` > > I suppose the capability to scope tenant context inside the xml load utility > could be provided in another way, e.g. adding an xml tag (for tenant). But, > currently that cannot be done.
Well, sometimes we have to give it a second look — and — search back into our memories for the correct answer. I did find what you were referring to, and yes - it does appear that the tenant context can be set in the XML file. Still, I don’t believe this works the way you’d want it. You won’t be able to load a set of tenants and their corresponding data in a single XML file. You could load a single tenant and not have to set the tenant with a system property. Which I believe is of limited value. So, my assertion stands (requires a new feature request) if not the original analysis. Thanks — Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
