Re: Unexpected behaviour for a transient field

2011-11-29 Thread Harald Wellmann
No, MyInterface is a plain old Java interface and not an entity. This interface extends another interface. Neither of these is serializable. Best regards, Harald 2011/11/28 Rick Curtis curti...@gmail.com: Harold - I'm quite surprised that we don't throw an exception, or warning in this case

Re: Unexpected behaviour for a transient field

2011-11-29 Thread Rick Curtis
Harold - Could I have you open a JIRA for this issue? I'm on the fence whether we should throw a exception, or just log a warning. Ideally an exception... but this has the potential to break existing applications when migrating between releases. Thanks, Rick On Tue, Nov 29, 2011 at 2:27 AM,

Re: Unexpected behaviour for a transient field

2011-11-29 Thread Harald Wellmann
Am 29.11.2011 16:12, schrieb Rick Curtis: Could I have you open a JIRA for this issue? Sure :-) https://issues.apache.org/jira/browse/OPENJPA-2083 Cheers, Harald

Re: Unexpected behaviour for a transient field

2011-11-28 Thread Rick Curtis
Harold - I'm quite surprised that we don't throw an exception, or warning in this case also. In the case that you mentioned, I assume MyInterface isn't an Entity type and doesn't extend Serializable? Thanks, Rick On Fri, Nov 25, 2011 at 6:00 AM, Harald Wellmann hwellmann...@googlemail.com

Unexpected behaviour for a transient field

2011-11-25 Thread Harald Wellmann
In a code review of an application using OpenJPA 2.1.1 with persistence mapping by annotations, I've just come across an entity class with a non-primitive field which is not annotated: private MyInterface myInterface; I would have put a @Transient annotation on that field (or better still,