[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-622?page=co... ] Lajos Gathy commented on HBX-622: --------------------------------- I also ran into this problem and I think I found an other solution, maybe it is a bit simpler: I noticed that the org.hibernate.cfg.reveng.ReverseEngineeringSettings class contains these properties: createManyToOneForForeignKey and createCollectionForForeignKey. They are both set to true, and you cannot set them on the Hibernate Code Generation Configurations dialog. But since I already had my own reveng strategy implementation (inherited from DelegatingReverseengineeringStrategy of course), I used the setSettings method to change these two properties to false: private ReverseEngineeringSettings settings; @Override public void setSettings(ReverseEngineeringSettings settings) { settings.setCreateManyToOneForForeignKey(false); settings.setCreateCollectionForForeignKey(false); this.settings = settings; super.setSettings(settings); } This way the generated POJOs did not contain the @ManyToOne/@OneToMany associations for the FKs (however there were some blank lines generated in the source). I am not sure, if this works with HT 3.1 (I used 3.2.4). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira