Posted under Eclipse
Permalink
Tags Bug, Eclipse, Gotcha, JPA
Sometimes eclipse lists the following error in the problem view :-
Class xxx is listed in the persistence.xml file but is not mapped
This appears to be a synchronisation problem within Eclipse, as deleting the classes from persistence.xml and then adding them back by browsing with Eclipse’s own persistence.xml editor eliminates the problem, even though the resulting file is identical. Validating the original file did not solve the problem.
Even with the error listed, projects still run and build successfully, so the problem is not serious.
I have also had other cases where Eclipse has whinged about a perfectly good persistence.xml, and have in general just lived with it as it is not serious.
This is an important issue to be aware of though to prevent much head scratching when such a problem is believed to be a real error and is not!
Leave a Reply
You must be logged in to post a comment.