Nope, at the moment I am using peers only. (But I intend to switch to nested ECs in new version for object creator/editor pages, which at the moment I do in session default EC and it is not good. Are there some non-obvious gotchas with nested ECs?)
Nevertheless I _do_ put just-created objects with temporary GIDs into relationships, and it looks like there would be some problem in there perhaps :/
On 2015-03-03, 2:47 PM, "OC" wrote:
Hello there,
in my latest log, there is (thrice) a NPE at
at er.extensions.eof.ERXDatabaseContextDelegate.batchFetchToOneFault(ERXDatabaseContextDelegate.java:714)
Looks like it's here:
===
private synchronized boolean batchFetchToOneFault(EODatabaseContext dbc, AutoBatchFaultingEnterpriseObject eo) {
if(fetchingToOne.canEnter(dbc)) {
try {
EOGlobalID sourceGID = eo.batchFaultingSourceGlobalID();
String key = eo.batchFaultingRelationshipName();
if(sourceGID != null && key != null) {
EOEditingContext ec = eo.editingContext();
AutoBatchFaultingEnterpriseObject source = (AutoBatchFaultingEnterpriseObject) ec.faultForGlobalID(sourceGID, ec);
EOEntityClassDescription cd = (EOEntityClassDescription)source.classDescription(); // 714
...
===
Looks like 'source' must have been null. Can faultForGlobalID return a null?!? When would that happen?
Thanks,
OC