Re: [eclipselink-users] Parsing exception description...can't do it
On Thu, Feb 10, 2011 at 4:12 PM, Laird Nelson <ljnelson@xxxxxxxxx>
It would appear that EclipseLink is complaining about this perfectly valid mapping. Or have I been doing something wrong here for months, and it's only now that EclipseLink (and no other JPA provider) has found it?
EclipseLink version 2.1.2 does not appear to complain about this. Perhaps you've completed some major refactoring since then? It looks like perhaps it can't see the code column that is mapped by the @MappedSuperclass ancestor.