Is this a bug, or am I missed something? Upon a save I am getting a
java.lang.IllegalStateException claiming a global ID could not be
obtained. This error cropped up after I converted a join table, for
which eos were not created, to an actual entity. I kept the same
attributes that made up a compound PK before, but changed them to FK
fields and added a separate, single field, PK. Now when I try to
save I get:
java.lang.IllegalStateException: A valid global ID could not be
obtained for entity named ScheduleDayProfileShiftProfile,
relationship named scheduleDayProfiles, primary key dictionary
{idShiftProfile = foo; idScheduleDayProfile = foobar; }.
As though it thinks the old compound PK is still defined. Has anyone
ever seen this? I have, and what I did last time was remove the
flattened relationships. I prefer not to do that this time. Can
anyone offer another solution?
--Brian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]