What I meant to say was, "Any ideas for fixing the modeler?" not "Any ideas
for fixing the model?"
The model works fine.
-Mike
Cris Daniluk <cris.danilu..mail.com> wrote:
> Seems like specifying a ConfigLoaderDelegate (using
> RuntimeLoadDelegate as the base) or an alternate ResourceLocator
> should do the trick.
>
> It's not automatic, but probably shouldn't be either...
>
> Cris
>
> On 5/26/05, Mike Kienenberger <mkienen..laska.net> wrote:
> > I have a model that references multiple maps in different locations.
> > It works fine from my applications (via the DefaultConfiguration
> > classloader).
> >
> > <domain name="ENG_WORK_MGMT">
> >
> > <map name="EngWorkMgmtMap"
> > location="com/gvea/eng_work_mgmt/model/EngWorkMgmtMap.map.xml"/>
> >
> > <map name="CoreWorkMgmtMap"
> > location="com/gvea/core_work_mgmt/model/CoreWorkMgmtMap.map.xml"/>
> >
> > <map name="AdminDbMap"
> > location="com/gvea/admindb/model/AdminDbMap.map.xml"/>
> >
> > </domain>
> >
> >
> > However, the modeler itself can't deal with the paths, probably because
it
> > only works with absolute file names.
> >
> > Is my only option to maintain two separate cayenne.xml files, one with
> > classpath-relative names, and the other with file-system relative names?
> >
> > Note that this file is stored in com/gvea/cayenne/model. Actually, that
> > gave me an idea. It does work if I move cayenne.xml to the root of my
src
> > directory. Not exactly what I want, but I suppose it's not the end of
the
> > world to have one file there.
> >
> > [Redirecting this to cayenne-devel instead of cayenne-user because the
real
> > question now becomes....]
> >
> > Any ideas for fixing the model to deal with the original layout? Or do
we
> > consider this an unsupportable configuration?
> >
This archive was generated by hypermail 2.0.0 : Thu May 26 2005 - 12:42:27 EDT