Interesting Tomcat (et al) Issue ...

From: Michael Gentry (Yes, I'm a Contractor) ("Michael)
Date: Wed Jul 13 2005 - 14:56:19 EDT

  • Next message: Mike Kienenberger: "Re: Interesting Tomcat (et al) Issue ..."

    Well, I guess interesting depends on your point of view.

    In my Eclipse/Tomcat/Tapestry development environment, I have a Java project
    that has a set of shared Cayenne objects in it (contains cayenne.xml/etc
    files plus all DbEntities). This project is currently used/referenced by
    two Tapestry-based utility application which run inside Tomcat. In order
    for Tomcat to see the Eclipse project, I added it to the CLASSPATH.
    Everything worked fine. Two Tapestry apps sharing a single Cayenne project.

    Then I started on #3 ...

    A new Tapestry-based utility with a different Cayenne model (new set of
    cayenne.xml/etc files and entities). Even though Tomcat has this project in
    the CLASSPATH, Cayenne is only finding the first cayenne.xml, which of
    course doesn't contain the right stuff for the new project. So, I can't
    create a new DataContext, even if I specify the right DataDomain. I don't
    mind specifying the domain using DataContext.createDataContext("MyDomain")
    so it can figure out which DataDomain I really care about, but it doesn't
    seem to load the second cayenne.xml file and add it's domains and I didn't
    see anything offhand to support this.

    Am I missing something here?

    Thanks!

    /dev/mrg

    PS. I can also see wanting to do this in a single application -- maintain
    multiple models for different layers of functionality ...

    This archive was generated by hypermail 2.0.0 : Wed Jul 13 2005 - 14:56:24 EDT