My goal is to use NHibernate schema generation along with Fluent NHibernate's automapper to generate my database. I'm having trouble with what I'll call "unidirectional many-to-many relationships."

Many of my entities have localized resources. A single class might look like this:

```
public class Something {
  public virtual int Id {get; private set;}
  public virtual Resource Title {get;set;}
  public virtual Resource Description {get;set;}
  public virtual IList<Resource> Bullets {get;set;}
}

```

The `Resource` class doesn't have any references back; these are entirely unidirectional.

```
public class Resource {
    public virtual int Id {get; private set;}
    public virtual IList<LocalizedResource> LocalizedResources {get;set;}
    // etc.
}
public class LocalizedResource { // 
    public virtual int Id {get; private set; }
    public virtual string CultureCode {get;set;}
    public virtual string Value {get;set;}
    public virtual Resource Resource {get;set;}
}

```

Without the `IList<Resource>`, everything is generated as I'd want -- Resource ID's are in the `Title` and `Description` fields. When I add in the `IList` though, NHibernate adds the field `something_id` to the `Resource` table. I understand why it does this, but in this situation it's not a sustainable approach.

What I want is to create a junction table for the bullets. Something like:

```
CREATE TABLE SomethingBullet (
  Id int NOT NULL PRIMARY KEY IDENTITY(1,1),
  Something_Id int NOT NULL,
  Resource_Id int NOT NULL
)

```

This way when I add the other twenty-odd entities into the database I won't end up with a ridiculously wide and sparse `Resource` table.

How do I instruct the Automapper to treat all `IList<Resource>` properties this way?