Poor exception handling on Invalid Mapping

[tch]

EclipseLink does a poor job handling invalid mappings. I had a bad
@Column annotation and wasted a bunch of time debugging it because
this was the only error EclipseLink would give:

Exception creating EntityManagerFactory using PersistenceProvider class

Um, OK! I finally recalled getting this same error a few months ago
and regenerated my Entities to fix it, but I estimate I've wasted
about 12 hours lifetime on this one "bug".

Am i missing someway to turn on better logging? I'm already at Finest,
if not I'll file a bug.

./tch
_______________________________________________
eclipselink-users mailing list
eclipselink-users@...
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

[James Sutherland]

It seems odd that that error was all you got.  Did it include a exception stack trace or caused by?  Were there any other errors logged to your log?  What exactly was the error?

If that was indeed all the info you got on the error then please log the bug.

Tim Hollosy wrote:

EclipseLink does a poor job handling invalid mappings. I had a bad
@Column annotation and wasted a bunch of time debugging it because
this was the only error EclipseLink would give:

Exception creating EntityManagerFactory using PersistenceProvider class

Um, OK! I finally recalled getting this same error a few months ago
and regenerated my Entities to fix it, but I estimate I've wasted
about 12 hours lifetime on this one "bug".

Am i missing someway to turn on better logging? I'm already at Finest,
if not I'll file a bug.

./tch

[tch]

That was indeed the only error I got, it just stopped in the middle of
processing all my annotations. I was able to duplicate by adding a
@Column annotation to a field that held a @OneToMany if that helps.


./tch



On Tue, Sep 30, 2008 at 11:54 AM, James Sutherland <jamesssss@...> wrote:

>
> It seems odd that that error was all you got.  Did it include a exception
> stack trace or caused by?  Were there any other errors logged to your log?
> What exactly was the error?
>
> If that was indeed all the info you got on the error then please log the
> bug.
>
>
>
> Tim Hollosy wrote:
>>
>> EclipseLink does a poor job handling invalid mappings. I had a bad
>> @Column annotation and wasted a bunch of time debugging it because
>> this was the only error EclipseLink would give:
>>
>> Exception creating EntityManagerFactory using PersistenceProvider class
>>
>> Um, OK! I finally recalled getting this same error a few months ago
>> and regenerated my Entities to fix it, but I estimate I've wasted
>> about 12 hours lifetime on this one "bug".
>>
>> Am i missing someway to turn on better logging? I'm already at Finest,
>> if not I'll file a bug.
>>
>> ./tch
>>
>
>
> -----
> ---
> http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland
> http://www.eclipse.org/eclipselink/
>  EclipseLink ,  http://www.oracle.com/technology/products/ias/toplink/
> TopLink
> Wiki:  http://wiki.eclipse.org/EclipseLink EclipseLink ,
> http://wiki.oracle.com/page/TopLink TopLink
> Forums:  http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink ,
> http://www.nabble.com/EclipseLink-f26430.html EclipseLink
> Book:  http://en.wikibooks.org/wiki/Java_Persistence Java Persistence
> --
> View this message in context: http://www.nabble.com/Poor-exception-handling-on-Invalid-Mapping-tp19729713p19744974.html
> Sent from the EclipseLink - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@...
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
>

_______________________________________________
eclipselink-users mailing list
eclipselink-users@...
https://dev.eclipse.org/mailman/listinfo/eclipselink-users