[OGo-Developer] NSConcreteEmptyDictionary (instance) does not recognize componentsJoinedByString

[Adam Tauno Williams]

Weird thing.  With the latest trunk I get this during
appointment_updateAction -

Nov 14 17:16:52 ogo-xmlrpcd-1.1 [3868]: >DirectAction> core on
exception: (Exception name:<nil> class:ObjcRuntimeException
reason:NSConcreteEmptyDictionary (instance) does not recognize
componentsJoinedByString: info:<nil>)
### child 3868 (#1) was terminated by signal 6 (uptime=14s).

If I set some log entries in the code - 

NSLog(@"%s: appointment_updateAction start", __PRETTY_FUNCTION__);
appointment = (SkyAppointmentDocument *)[self
getDocumentByArgument:_arg];
NSLog(@"%s: appointment_updateAction app retrieved",
__PRETTY_FUNCTION__);
if (appointment == nil) {
  return [self faultWithFaultCode:XMLRPC_FAULT_INVALID_RESULT
               reason:@"No appointment for argument found"];
}
NSLog(@"%s: appointment_updateAction app valid", __PRETTY_FUNCTION__);
[self _takeValuesDict:_arg toAppointment:&appointment];
NSLog(@"%s: appointment_updateAction app taken", __PRETTY_FUNCTION__);
[[self appointmentDataSource] updateObject:appointment];
NSLog(@"%s: appointment_updateAction app updated", __PRETTY_FUNCTION__);
NSLog(@"%s: appointment_updateAction end", __PRETTY_FUNCTION__);

 - I get -

Nov 14 17:27:04 ogo-xmlrpcd-1.1 [4204]: -[DirectAction(Appointment)
appointment:updateAction:]: appointment_updateAction start
Nov 14 17:27:04 ogo-xmlrpcd-1.1 [4204]: -[DirectAction(Appointment)
appointment:updateAction:]: appointment_updateAction retrieved
Nov 14 17:27:04 ogo-xmlrpcd-1.1 [4204]: -[DirectAction(Appointment)
appointment:updateAction:]: appointment_updateAction app valid
Nov 14 17:27:04 ogo-xmlrpcd-1.1 [4204]: >DirectAction> core on
exception: (Exception name:<nil> class:ObjcRuntimeException
reason:NSConcreteEmptyDictionary (instance) does not recognize
componentsJoinedByString: info:<nil>)
### child 4204 (#1) was terminated by signal 6 (uptime=54s).
  
So it looks like it is coming from the _takeValuesDict invocation. Has
something been changed in the DocAPI recently?  Seems wierd.