- This topic has 1 reply, 2 voices, and was last updated 19 years, 4 months ago by
.
-
Posts
-
The problem: Every time I create a new hibernate mapping using the MyEclipse wizard, the hibernate.cfg.xml file contains all mappings that I’ve ever created in that project, even those I deleted. This causes error messages, since the necessary classes no longer exist.
The reason for this is probably that in the file .myhibernatedata all mappings I’ve ever created still exist as “config.mapping”-properties, so the bugfix would probably be to update this .myhibernatedata file properly when mappings are deleted.
My Environment:
– Win XP, V2002, Service Pack 2
– j2sdk1.4.1_02
– Eclipse 3.0.1, Build id 200409161125
– MyEclipse 3.8.4, Build id: 200501171200-3.8.4retoinform,
I see your problem – it was quite easy to replicate; and your reasoning is correct as well.
We have a brand new Hibernate configuration file editor in ME4.0, and this problem does not exist there.
You can either wait for 4.0 to go GA or pick up one of the BETA Milestones from the Development Releases section under Downloads.
Sorry for the inconvenience caused,
Brian.
