Hi,
I've bumped into this several times.
The problem is that enterprise objects do NOT have any primary key
right after creation until they are saved into database.
So when you create new instance of enterprise object (new record into
database) you should run EditingContext.saveChanges() before you can
access the primary key of you object.
Regards,
Gennady Kushnir
On 13.07.2006, at 13:46, David Griffith wrote:
Hi all,
In an application that has been working great for a long time,
suddenly I am getting this error:
[2006-07-13 11:19:22 CEST] <WorkerThread1>
java.lang.NullPointerException
at com.webobjects.eoaccess.EOUtilities.primaryKeyForObject
(EOUtilities.java:834)
at Customer.custID(Customer.java:46)
at EditCustomer.saveChanges(EditCustomer.java:94)
This is when the Customer class is attempting to get the Primary
Key for the current record.
On further investigation I have realised that the Customer object
is not being saved at all, it appears as though it is unable to get
a Primary Key for the record as it saves it. The EO_PK_TABLE
appears fine and all other tables save with no problem.
I wonder does anyone have any idea where I should look to find the
problem, I have checked everything and it all looks as it did before.
Kind regards,
David.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/genkush%
408ka.mipt.ru
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com
