Re: Where should a shared EOModel live?

From: Cedarstone (gile..edarstone.co.uk)
Date: Thu Jun 07 2007 - 08:15:10 EDT

  • Next message: Anjo Krank: "Re: project templates"

    Hi

    Thanks for this and I guess both should work ok. However if you add
    the EOModel in to a project as a "Linked Source" file then you get
    the nice icon appearing in the project folder view and you can double
    click and edit from there, which may be handy.

    Thanks

    Giles

    > Hi,
    >
    > Moving eomodel to a framework is a good idea. You can add a
    > framework project dependency via Java Build Path - Projects.
    >
    > On Jun 7, 2007, at 4:00 PM, Cedarstone wrote:
    >
    >> Hi
    >>
    >> Answering my own question. I have created a new WOFramework that
    >> just holds the EOModel then for each WO project I have pointed at
    >> the model by adding it in as a "Source" folder in the build path.
    >> This seems to have worked and Eclipse/WOLips recognises it.
    >>
    >> Let me know if this is the wrong way to go about it.
    >>
    >> Thanks.
    >>
    >> Giles
    >>
    >>> Hi
    >>>
    >>> Simple question really. We are just in the process of switching
    >>> to WOLips and have multiple WO projects that share a common EOModel.
    >>> What is the proper way to arrange WOLips/Eclipse so each project
    >>> points to just the one version of the EOModel?
    >>>
    >>> I have created an Eclipse project to hold the EOModel but I do
    >>> not seem to be able to point the various WO projects to it so
    >>> they can see it. Before I waste too much time can somebody tell
    >>> me how this should be done/arranged.
    >>>
    >>> Many thanks
    >>>
    >>> Giles
    >>
    >>
    >
    > --
    > Denis Frolov
    > Design Maximum MA
    >
    > Tel: +7 863 2648211
    > Fax: +7 863 2645229
    > Web: http://www.designmaximum.com
    >
    >
    >

    This archive was generated by hypermail 2.0.0 : Thu Jun 07 2007 - 08:16:01 EDT