Re: You crossed editing context boundaries...
Re: You crossed editing context boundaries...
- Subject: Re: You crossed editing context boundaries...
- From: WebObjects <email@hidden>
- Date: Wed, 15 Oct 2008 09:58:11 -0500
Aha, I need the CreationDate in the EmployeeXTurn table because I
will need to know sometimes when was created the turn by the employee,
for administrative reasons.
So following your advise I will need to make the relatonship again,
but this time I shouldn't flattened (im not familiar with the
term ;-)) ... ok let me see if I can do it, the only problem i see, is
that i tried once to leave id as the only PK, but then when trying to
make the relationship, EOModeler complained when trying to make the
relationship to attributes that weren't PK, Im gonna try it once
again.. I will let you know.
Gus
PS taking care of babies and trying to programing.... hard work.
On Oct 14, 2008, at 10:32 PM, David LeBer wrote:
On 14-Oct-08, at 10:19 PM, WebObjects wrote:
mmm.. weird I tried to add it one by one using the
addObjectToBothSidesOfRelationshipWithKey() method
and it stills giving me the java.lang.nullpointerexception
:S:S:S:
maybe something wrong with my EOModel???
Im attaching it..
<ScheduleControl.eomodeld>
The join table between Employee and Turn looks whacked.
- It has a three way compound primary key. (employeeId, id, turnId)
- It has a 'creationDate' attribute.
- It participates in a flattened relationship between Employee and
Turn.
EOF is not going to know how generate that three way compound
primary key.
If EmployeeXTurn is just a join table and is going to be flattened
out of the object graph then it should just have a 2 way compound PK
based on the FKs from Employee and Turn and it should NOT have any
other attributes.
If EmployeeXTurn has attributes you need to gain access to (i.e.
creationDate) then you should treat it like a standard EO.
- Remove the flattened relationships from Employee to Turn
- Expose the relationships from Employee and Turn to EmployeeXTurn
- Use only id as the PK.
- Manage the creation of EmployeeXTurn manually.
apart of the consistency names and other stuff, are the relations
good?
Regards
Gus
On Oct 14, 2008, at 7:43 PM, Ricardo J. Parada wrote:
How about your registerTurns() method? Did you change it to use
myEC instead of ERXEC.newEditingContext()?
On Oct 14, 2008, at 8:17 PM, WebObjects wrote:
aha... you are right, after whole day sitting here, I didn't
realize I had teh emp at login with the
session().defaultEditingContext, and here at PaguinaUsuario I m
using another one.
My mind its kind of distracted...
I made the changes, and still Im getting the nullpointerexception
java.lang.NullPointerException
[2008-10-14 19:13:51 COT] <WorkerThread0>
java.lang.NullPointerException
at
com
.webobjects
.eoaccess
.EODatabaseContext
._objectFaultWithSnapshotRelationshipEditingContext
(EODatabaseContext.java:2356)
at
com
.webobjects
.eoaccess
.EODatabaseContext
._fireDeferredFaultWithSourceObject(EODatabaseContext.java:2401)
at
com
.webobjects
.eoaccess
.EOAccessDeferredFaultHandler
.createFaultForDeferredFault(EOAccessDeferredFaultHandler.java:49)
at
com
.webobjects
.eocontrol
.EOCustomObject.willReadRelationship(EOCustomObject.java:1279)
at
er
.extensions
.eof.ERXGenericRecord.willReadRelationship(ERXGenericRecord.java:
348)
at com.webobjects.eocontrol._EOMutableKnownKeyDictionary
$Initializer
$
_LazyGenericRecordBinding
.valueInObject(_EOMutableKnownKeyDictionary.java:614)
at
com
.webobjects
.eocontrol.EOCustomObject.storedValueForKey(EOCustomObject.java:
1634)
at
com
.webobjects
.eoaccess
.EODatabaseContext
.databaseOperationForObject(EODatabaseContext.java:4814)
at
com
.webobjects
.eoaccess.EODatabaseContext.valuesForKeys(EODatabaseContext.java:
6535)
at
com
.webobjects
.eocontrol
.EOObjectStoreCoordinator
.valuesForKeys(EOObjectStoreCoordinator.java:326)
at com.webobjects.eoaccess.EOQualifierSQLGeneration
$
_KeyValueQualifierSupport
.schemaBasedQualifierWithRootEntity(EOQualifierSQLGeneration.java:
439)
at er.extensions.ERXExtensions
$
KeyValueQualifierSQLGenerationSupport
.schemaBasedQualifierWithRootEntity(ERXExtensions.java:304)
at com.webobjects.eoaccess.EOQualifierSQLGeneration
$
Support
._schemaBasedQualifierWithRootEntity
(EOQualifierSQLGeneration.java:179)
at
com
.webobjects
.eoaccess
.EODatabaseChannel
.selectObjectsWithFetchSpecification(EODatabaseChannel.java:227)
and more........ much more.
On Oct 14, 2008, at 7:06 PM, Ricardo J. Parada wrote:
It looks like you got the employee object using the session's
default editing context. And you are saying that your
PaginaUsuario creates its own editing context in the
constructor. So there you have it: two different editing
contexts.
I would modify your setEmp() method in the PaginaUsuario that
you make a copy of the emp object passed in to the editing
context used in that page. Something like this:
public void estEmp(Employee anEmp) {
emp = anEmp.localInstanceIn(myEC);
}
Then your registerTurns() method is yet creating another editing
context. Shouldn't that be also myEC??
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
;david
--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
twitter: http://twitter.com/rebeld
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden