I had a thought that I could wire up beans using Spring IOC. From there I could instantiate and export as XML. However, I'm digging through, trying to find my parent level class, and not having much luck. And even if/when I do, there's the question of having GUIDs on entries: are they required for initial import? If they're all contained within a singular domain content file, do they know their proper parent association when relevant?
Beyond being repeatable configuration, this would allow for iterative and better consistency in naming and linking, and avoiding my often scenario of "oops, forgot to create this piece first". Is what I'm wanting to do feasible, or is the web console the only way to build out content? thank you for your guidance! On Fri, Apr 5, 2019, 12:46 PM Adam Levine <[email protected]> wrote: > I like to keep initial structuring in a repeatable form. For instance, I > have LDIFs I import to build out my custom schema, and then the LDAP > hierarchy itself, and then seed with base content. Recreating this by hand > is not something anyone wants to do. > > With that, is there a way to build out content to feed MasterContent.xml, > other than wiring everything in the GUI and exporting? I could edit the > XML by hand, but that, too, looks fragile if it's dependent upon correct > GUID cross-references. > > Thank you ! >
