| Re: [eclipselink-users] Parsing exception description...can't do it |
Please file the bug in Eclipse bugzilla. Laird Nelson wrote:
OK; thanks. You might want to ping the Glassfish 3.1 guys as this will probably show up in their release candidate. Do you want me to file the bug in Glassfish's jira?LOn Thu, Feb 10, 2011 at 4:20 PM, Tom Ware <tom.ware@xxxxxxxxxx <mailto:tom.ware@xxxxxxxxxx>> wrote:Hi Laird, This appears to be a bug. Please file a bug. -Tom Laird Nelson wrote: On Thu, Feb 10, 2011 at 4:12 PM, Laird Nelson <ljnelson@xxxxxxxxx <mailto:ljnelson@xxxxxxxxx> <mailto:ljnelson@xxxxxxxxx <mailto:ljnelson@xxxxxxxxx>>> wrote: 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. L ------------------------------------------------------------------------ _______________________________________________ eclipselink-users mailing list eclipselink-users@xxxxxxxxxxx <mailto:eclipselink-users@xxxxxxxxxxx> https://dev.eclipse.org/mailman/listinfo/eclipselink-users _______________________________________________ eclipselink-users mailing list eclipselink-users@xxxxxxxxxxx <mailto:eclipselink-users@xxxxxxxxxxx> https://dev.eclipse.org/mailman/listinfo/eclipselink-users ------------------------------------------------------------------------ _______________________________________________ eclipselink-users mailing list eclipselink-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-users