If you can change your domain model, take a look at answer given by cletus. You'll only have one table to update so it'll provide better performance.
If you cannot change your domain model, you can map your comment
collections via join tables:
// ENTRY
@OneToMany
@JoinTable(
name="ENTRY_COMMENTS",
joinColumns = @JoinColumn( name="entry_id"),
inverseJoinColumns = @JoinColumn( name="comment_id")
)
public List<Comment> getComments()
// ISSUE
@OneToMany
@JoinTable(
name="ISSUE_COMMENTS",
joinColumns = @JoinColumn( name="issue_id"),
inverseJoinColumns = @JoinColumn( name="comment_id")
)
public List<Comment> getComments()
Your comments would still be in the same table for both issues and entries; only join tables will be different. Note that this is a uni-directional relationship. Details are here