Re: DI-based configuration works

From: Andrus Adamchik (andru..bjectstyle.org)
Date: Tue Dec 08 2009 - 09:57:03 EST

  • Next message: Michael Gentry: "Re: DI-based configuration works"

    Actually it may end up being merged into cayenne-modeler module at
    some point. My thinking was also that there is a faint possibility
    that somebody other than the modeler might need it (Maven/Ant tasks?).

    Andrus

    On Dec 8, 2009, at 9:51 AM, Andrus Adamchik wrote:

    > Reading projects will stay in cayenne-jdk1.5-unpublished
    > (o.a.c.configuration). So nothing is going to change on the user end.
    >
    > Reading/writing will go into this new module, imported by the
    > Modeler. So cayenne-project-unpublished will not be included in
    > cayenne-server.jar or cayenne-client.jar, but will be included in
    > the Modeler assemblies, e.g. CayenneModeler.app.
    >
    > Andrus
    >
    > On Dec 8, 2009, at 9:46 AM, Michael Gentry wrote:
    >
    >> I guess I'm confused as to where it will reside when published, then.
    >> You are talking about the Cayenne models (XML files) that need to be
    >> loaded by both the server and the modeler (does ROP need them, too?)
    >> and that need to be saved by the modeler, right?
    >>
    >> Thanks,
    >>
    >> mrg
    >>
    >>
    >> On Tue, Dec 8, 2009 at 9:41 AM, Andrus Adamchik <andru..bjectstyle.org
    >> > wrote:
    >>> It will be an "unpublished" module, and yes, only the Modeler will
    >>> be
    >>> importing it now. I sort of like to keep things modular as long as
    >>> it
    >>> doesn't create user confusion (which I think it doesn't in this
    >>> case).
    >>>
    >>> Andrus
    >>>
    >>> On Dec 8, 2009, at 9:26 AM, Michael Gentry wrote:
    >>>
    >>>> Is creating a separate module needed or would that just add more
    >>>> confusion? Would there be yet another JAR that shows up in the
    >>>> Maven
    >>>> repository for people to have to decide what they want?
    >>>>
    >>>> Seems to me the server side needs to be able to load the model, but
    >>>> only the Modeler needs to be able to save.
    >>>>
    >>>> mrg
    >>>>
    >>>>
    >>>> On Tue, Dec 8, 2009 at 7:49 AM, Andrus Adamchik <andru..bjectstyle.org
    >>>> >
    >>>> wrote:
    >>>>>
    >>>>> I been thinking about this step, and decided against moving
    >>>>> o.a.c.conf to
    >>>>> the Modeler. Instead I am going to create a separate new module
    >>>>> cayenne-project-unpublished, implementing project saving/loading
    >>>>> functionality with the Modeler use in mind. Once this is done, the
    >>>>> Modeler
    >>>>> and runtime can be switched to the new stack simultaneously, and
    >>>>> o.a.c.conf
    >>>>> and o.a.c.project removed from the runtime jars.
    >>>>>
    >>>>
    >>>
    >>>
    >>
    >
    >



    This archive was generated by hypermail 2.0.0 : Tue Dec 08 2009 - 09:57:32 EST