Re: Cocoa Cayenne status

From: Watkins, Garry (gwatkin..otleyrice.com)
Date: Sun Aug 27 2006 - 22:05:00 EDT

  • Next message: Tore Halset: "Re: Cocoa Cayenne status"

    Cool, I have been pretty busy catching up, with work since WWDC. However, I
    spent about 12 hours working on it this weekend. I spent most of yesterday
    just trying to get the 3t stuff working. I ran into the error 500 with
    Hessian 3.0.20. I finally had to track down a 3.0.13. But I got it going
    late last night.

    For the CoreData stuff, I have written the following:

        Extended
            NSManagedObjectContext - which should encompass faulting
            NSPersistentStoreCoordinator
            NSManagedObjectID

        Created my own classes since these aren't exposed by CD
            ObjectStore
            TransactionalObjectStore
            CayenneObjectStore (I am just starting implementing this)
            WebObjectsObjectStore (Planned for the future)

    All of the above have not been tested yet, since they all work together.
    Hopefully, I will have some time this week and we will get to integrate it
    all together with the stuff that you have been doing.

    Garry

    On 8/27/06 6:28 PM, "Tore Halset" <halse..vv.ntnu.no> wrote:

    > Hello.
    >
    > I got faults working now :) See attached screenshot of the tutorial
    > client app in Cocoa.
    >
    > I have not done anything with the Core Data-side of it yet, but
    > bindings are working out of the box. In the example app, there is one
    > NSArrayController for Persons and one for Paintings. The paintings-
    > controller are autoupdated (using bindings) from the selection-array
    > of the persons-controller. Pressing the Query-button will manually
    > (in code) set the content array of the persons-controller. Any
    > progress on the Core Data side of it Garry?
    >
    > There are still some issues with the HessianObjC-framework. I am
    > currently using an unaccepted patch for circular refs. It was not
    > accepted as Objective-C has issues with circular refs. Will have to
    > use Weak refs or something.. This is caused by the fact that DataMap
    > has some objects that has refs to the DataMap. In practice, the leak
    > are non-existant as we only need a single instance of the
    > EntityResolver.
    >
    > Done:
    > * Faults.
    > * Edit/commit simple property. Like changing the artist og painting
    > name.
    >
    > Todo:
    > * Add/delete objects. I hope to get this working using bindings and
    > the array-controller as well..
    > * Core Data stuff.
    > * fix authentication and object refs in HessianObjC.
    > * separate existing project into framework and example client.
    > * rollback, NSUndoManager etc.
    > * +++
    >
    > - Tore.

    -- 
    Garry Watkins
    

    Database Administrator Motley Rice LLC 843-216-9639

    Confidential & Privileged

    Unless otherwise indicated or obvious from its nature, the information contained in this communication is attorney-client privileged and confidential information/work product. This communication is intended for the use of the individual or entity named above. If the reader of this communication is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error or are not sure whether it is privileged, please immediately notify us by return e-mail and destroy any copies--electronic, paper or otherwise--which you may have of this communication.



    This archive was generated by hypermail 2.0.0 : Sun Aug 27 2006 - 22:14:50 EDT