I agree with Joshua - web container application ClassLoaders already
provide a solution to the original problem of deploying multiple apps
(not sure how well it plays with Eclipse Sysdeo plugin as I mostly
use Jetty/JettyLauncher)..
However allowing to save cayenne.xml under some other name is useful
functionality in general, and besides it is very easy to implement.
+1 for this feature.
Also I guess if you load multiple configurations in the same
ClassLoader space, you should avoid setting singleton shared
Configuration the way Cayenne does by default. Instead you may have
to manage Configuration instances yourself at the application level
(e.g. set it as a Tapestry "global").
Andrus
On Jul 14, 2005, at 2:32 AM, John Martyniak wrote:
> this sounds like a good idea.
>
> -John
>
> On Jul 13, 2005, at 5:12 PM, Gentry, Michael ((Contractor)) 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
>>
>
This archive was generated by hypermail 2.0.0 : Thu Jul 14 2005 - 01:43:58 EDT