You can Use the M-N relationship:

public class Route
{
    ...

    @Persistent
    @Join(column="ROUTE_ID")
    @Element(column="PROVIDER_ID")
    Set<Provider> provider;



}

public class Provider
{
    ...

    @Persistent(mappedBy="providers")
    Set<Route> routes;
}



On Tue, Jan 22, 2013 at 2:10 AM, Christian Steinebach <
[email protected]> wrote:

> Hi,
>
> In case:
>
> - A transport service providers serves several routes
> - A route may be served by several transport service providers
>
> How can this many to many relationship be modeled in Isis?
>
> In the example application one ToDoItem may only appear in ONE
> dependency list.
>
>            Christian

Reply via email to