You know your model better than I so this might not make sense but I'll make a suggestion anyway...
A ManyToOne doesn't generate any methods in the child object, so unless
you add that logic seperately (to a decorator) you won't be able to
traverse from your publisher object to the endorsements.
Looking at the definition of PUBLISHER_ENDORSEMENTS, it doesn't seem to have anything other than two foreign keys that make up it's own primary key (A classic join table).
If that's the case I would suggest you either choose a Many to Many from publisher to endorsements (or vise versa if endorsement is more important), or a combination of One to Many and Many to One. But either way the real objects you seem to care about are the publisher and endorsement, not the join.
Then you'd just get a publisher object and have the collections methods to get access to the endorsements that are related.
I know some of this might sound like klingon, if you used to thinking of tables and queries transfer takes a little bit of a mind shift.
Basically I'd suggest you try this with a
publisher manytomany endorsements
or
publisher onetomany publisher_endorsments manytoone endorsments
If that model really is what you want, you won't be able to traverse from publisher to endorsement without writing some custom logic in a decorator or you'd have to resort to sql to retrieve keys...
Again this is just a suggestion, so take it with a grain of salt.