"Gentry, Michael (Contractor)" <michael_gentr..anniemae.com> wrote:
> The more I'm thinking about this the more I think the best solution
> would be to modify the modeler to allow you to specify the filename
> (such as foo.cayenne and bar.cayenne) and then modify the Cayenne
> configuration process to load all *.cayenne XML files it finds in the
> CLASSPATH. This would give you the most flexibility, eliminate this
> development and potential production choke point (1), and even allow you
> to associate *.cayenne files with an application instead of just a
> generic XML file.
>
> Any thoughts?
Sounds good to me.
Might be a problem if shared code has some cayenne config files (like a
cayenne-testing.xml) that you don't want loaded all the time, but creative
filenaming could deal with that.
Maybe there should only be one cayenne.xml file, but allow multiple
cayenne-module.xml files.
-Mike
This archive was generated by hypermail 2.0.0 : Wed Jul 13 2005 - 17:27:13 EDT