Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] Question on initial "field values"

Yes, I have tried marking it as Transient.. Yes it is possible this
field was set in a previous session.  Can you point me to the place
where I could get some more info on the descriptor merge event you refer
to?  Are there code examples for this?

-----Original Message-----
From: eclipselink-users-bounces@xxxxxxxxxxx
[mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of James
Sutherland
Sent: Wednesday, November 24, 2010 9:32 AM
To: eclipselink-users@xxxxxxxxxxx
Subject: Re: [eclipselink-users] Question on initial "field values"


Have you marked the fields as @Transient?

For the existing object, were these fields set previously?  They may
still
have the existing values from the persistence context, or shared cache.
If
you do not want them cached you can clear them using a descriptor merge
event, or instantiation copy policy.



khaskett wrote:
>
> I have a domain object that extends a "base domain" object. This base
> domain object has some Boolean fields that aren't fields on the table
> but are there to track certain changes that might occur during the
> lifetime of the domain object.  It seems fine when I do a "new" on the
> object the fields are defaulted to "false" correctly, but when I do a
> find on an existing object, the values for these tracking fields seem
to
> be mixed.
>
>
>
> abstract class BaseBomainClass {
>
>
>
> private Boolean trackingfield;
>
>
>
> setTrackingfield(Boolean){..
>
>
>
> getTrackingField()..
>
>
>
> }
>
>
>
> public class DomainClass extends BaseDomainClass {
>
> ...
>
> }
>
>
>
> How are these field values set?
>
>
>
> Thanks
>
> Kevin
>
>
> This message (including any attachments) is intended only for
> the use of the individual or entity to which it is addressed and
> may contain information that is non-public, proprietary,
> privileged, confidential, and exempt from disclosure under
> applicable law or may constitute as attorney work product.
> If you are not the intended recipient, you are hereby notified
> that any use, dissemination, distribution, or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, notify us immediately by telephone and
> (i) destroy this message if a facsimile or (ii) delete this message
> immediately if this is an electronic communication.
>
> Thank you.
>
>


-----
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
Blog:  http://java-persistence-performance.blogspot.com/ Java
Persistence
Performance
--
View this message in context:
http://old.nabble.com/Question-on-initial-%22field-values%22-tp30283464p
30297736.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.

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

This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.

Thank you.


Back to the top