More pros: * Templates be edited by an external tool without having to export the original data then import it after making changes.
* Individual templates remain under version control. On Fri, Apr 8, 2016 at 11:12 AM, Michael Gentry <[email protected]> wrote: > So, I've had another thought on this ... > > We could store the custom templates, JavaDoc, etc. in a separate XML file. > This information is really only useful for class generation, either in > Cayenne Modeler or cgen. > > > Pros: > > * Class generation data wouldn't clutter up the current XML mapping file. > * Separate file can be omitted/excluded by the build tool, such as Maven, > so it isn't packaged up in your JAR/WAR for deployment. > * Class generation data wouldn't get loaded at run-time, which is more > memory efficient for your server processes. > > Cons: > > * More difficult to implement/manage since there'd be duplication of > information to tie the two files together. > > > I think the pros outweigh the cons. Thoughts? > > Thanks, > > mrg
