Yeah, it is little weird, but that's how the API is structured.  The classes are the low level stuff, individual steps and pieces, and the functions are bundles of functionality that represent whole actions.  I think the entry ownership is ultimately set through a separate method call, so perhaps the half way point here is to call the entry ownership method after the writeEntry method.  But that duplicates logic that is already worked up in the function, so I'd just call the function instead of replicating functionality that already exists there.