What is _bServices? If it's anything but your controller, you're
"changing the array behind the controller's back". You must either:
a) Call -willChangeValueForKey: and -didChangeValueForKey: before/
after changing the array, or,
b) Call -addObject: against your array controller.
You really should not do (b) from model-level code, because you should
not be using controller objects to manipulate your model objects.
Instead, send -mutableArrayValueForKey: or -mutableSetValueForKey: to
a model object that has a to-many relationship which you want to
change. The result of those messages will be an NSMutableArray or
NSMutableSet that you can manipulate which will ultimately modify the
appropriate relationship of your object, and will ensure that
appropriate KVO notifications are posted.
While the standard Xcode templates don't create separate "Model,"
"View," and "Controller" folders in new projects, you should still
remember to partition your application along those lines. Cocoa was
Opinionated Software[1] before Ruby on Rails was a gleam in DHH's eye;
it's designed to help you build software that follows a Model-View-
Controller architecture. If you stray from that by working across
layers and so on, you'll start going against the grain of the
framework and things will become more difficult and confusing.
(A good example of the latter is that people who *do* try to use (b)
above to manipulate relationships at the model level get confused when
they try to debug their code. A distressingly common question on the
list is, "I sent -addObject: to my controller, why didn't the
collection it's bound to change immediately?")
