Grokbase Groups Cayenne dev May 2006
FAQ
I have been running into some issues with WO/EO that have been driving me
nuts lately, like giving me Object not available errors, for optional to one
relationships.

My question is "Could Cayenne be used as a near drop in replacement for
Enterprise Objects within a WO app server?" I think if we could implement
key value coding, then it would be fairly simple to port some wo apps.

Thanks
--
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.

Search Discussions

  • Gentry, Michael \(Contractor\) at May 12, 2006 at 3:09 pm
    Well, Cayenne already supports most of KVC.

    There was a thread on the Cayenne User List, "where to put Cayenne.xml",
    which started on April 1 (no joke) that talks about using Cayenne as an
    EOF replacement in WO. Hopefully that can answer your immediate
    questions.

    /dev/mrg


    -----Original Message-----
    From: Watkins, Garry
    Sent: Friday, May 12, 2006 10:57 AM
    To: cayenne-dev@incubator.apache.org
    Subject: Could Cayenne be used as a near drop in replacement for
    Enterprise Objects within a WO environment?


    I have been running into some issues with WO/EO that have been driving
    me
    nuts lately, like giving me Object not available errors, for optional to
    one
    relationships.

    My question is "Could Cayenne be used as a near drop in replacement for
    Enterprise Objects within a WO app server?" I think if we could
    implement
    key value coding, then it would be fairly simple to port some wo apps.

    Thanks
    --
    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.
  • Watkins, Garry at May 12, 2006 at 6:23 pm
    Thanks for the guidance.

    A few more questions, about some of the things that I ran into before, that
    I was wanting resolved before I made the switch over.

    I am using NestedECs a bunch, is Cayenne's nested dataContext working
    yet?

    Does Cayenne have an EOGenericRecord equivalent yet?


    Can I just use a .eomodeld instead of a cayenne.xml?

    Thanks
    Garry


    On 5/12/06 11:08 AM, "Gentry, Michael (Contractor)"
    wrote:
    Well, Cayenne already supports most of KVC.

    There was a thread on the Cayenne User List, "where to put Cayenne.xml",
    which started on April 1 (no joke) that talks about using Cayenne as an
    EOF replacement in WO. Hopefully that can answer your immediate
    questions.

    /dev/mrg


    -----Original Message-----
    From: Watkins, Garry
    Sent: Friday, May 12, 2006 10:57 AM
    To: cayenne-dev@incubator.apache.org
    Subject: Could Cayenne be used as a near drop in replacement for
    Enterprise Objects within a WO environment?


    I have been running into some issues with WO/EO that have been driving
    me
    nuts lately, like giving me Object not available errors, for optional to
    one
    relationships.

    My question is "Could Cayenne be used as a near drop in replacement for
    Enterprise Objects within a WO app server?" I think if we could
    implement
    key value coding, then it would be fairly simple to port some wo apps.

    Thanks
    --
    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.
  • Mike Kienenberger at May 12, 2006 at 6:39 pm

    On 5/12/06, Watkins, Garry wrote:
    I am using NestedECs a bunch, is Cayenne's nested dataContext working
    yet?
    I think so, but Andrus would know for sure.

    Does Cayenne have an EOGenericRecord equivalent yet?
    Yes, but I don't know if it's been seriously tested yet.

    Can I just use a .eomodeld instead of a cayenne.xml?
    No, but the modeler can read it in and save it back out as cayenne.xml.
  • Andrus Adamchik at May 12, 2006 at 10:01 pm

    On May 12, 2006, at 2:39 PM, Mike Kienenberger wrote:
    On 5/12/06, Watkins, Garry wrote:
    I am using NestedECs a bunch, is Cayenne's nested dataContext
    working
    yet?
    I think so, but Andrus would know for sure.
    Yep, nested DataContexts are fully supported.

    Does Cayenne have an EOGenericRecord equivalent yet?
    Yes, but I don't know if it's been seriously tested yet.
    Still it should work ok, as a generic record in Cayenne is just a
    CayenneDataObject, same as used as a common superclass already.

    Can I just use a .eomodeld instead of a cayenne.xml?
    No, but the modeler can read it in and save it back out as
    cayenne.xml.
    Theoretically you can customize the runtime to load an EOModel
    directly ... although there may be some issues converting inheritance
    and fetch specs, so you' probably want to import the EOModel in the
    Modeler, fix anything that doesn't look right, and then save as a
    Cayenne project.

    Andrus
  • Watkins, Garry at May 14, 2006 at 5:45 pm
    Thanks Andrus,

    I am going to try and help you guys out again. It has been over a year
    since I contributed anything. Any way, I am currently working on the
    EOModel import routine. I found some issues with it, and I just about have
    a patch to fix those items. I will open up a Jira issue once I get done.

    I really am interested in making EOModels work instead of Cayenne.xml,
    because I want to use WOBuilder and have the key completion work with
    EOGenericRecords. I will be building a WOCompatibility framework to address
    those needs. So if anyone has any ideas about what I should add please let
    me know.

    Thanks
    Garry
    On 5/12/06 6:00 PM, "Andrus Adamchik" wrote:

    On May 12, 2006, at 2:39 PM, Mike Kienenberger wrote:
    On 5/12/06, Watkins, Garry wrote:
    I am using NestedECs a bunch, is Cayenne's nested dataContext
    working
    yet?
    I think so, but Andrus would know for sure.
    Yep, nested DataContexts are fully supported.

    Does Cayenne have an EOGenericRecord equivalent yet?
    Yes, but I don't know if it's been seriously tested yet.
    Still it should work ok, as a generic record in Cayenne is just a
    CayenneDataObject, same as used as a common superclass already.

    Can I just use a .eomodeld instead of a cayenne.xml?
    No, but the modeler can read it in and save it back out as
    cayenne.xml.
    Theoretically you can customize the runtime to load an EOModel
    directly ... although there may be some issues converting inheritance
    and fetch specs, so you' probably want to import the EOModel in the
    Modeler, fix anything that doesn't look right, and then save as a
    Cayenne project.

    Andrus
    --
    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.
  • Watkins, Garry at May 14, 2006 at 9:23 pm
    How does Cayenne support derived columns (from an EOModel) in a DbEntity? I
    am working on the import of an EOModel derived column formula, and it
    appears that my import is good.

    However, it looks like Cayenne Modeler does not support a DerivedDbAttribute
    in a regular DbEntity? Is that true? Does the framework support that
    combination? If that is true, then I won't worry about the modeler GUI not
    showing it correctly.

    This is what I have from the EOModel plist for the attribute:

    attributes = (
    {
    allowsNull = Y;
    definition = "dbo.years_diff(tsDateOfBirth, tsDateOfDeath,
    GETDATE())";
    name = age;
    valueClassName = NSNumber;
    valueType = l;
    }, ...)

    I create a DbDerivedAttribute called AGE, with the definition is the spec.

    Thanks
    Garry

    On 5/14/06 1:45 PM, "Watkins, Garry" wrote:

    Thanks Andrus,

    I am going to try and help you guys out again. It has been over a year
    since I contributed anything. Any way, I am currently working on the
    EOModel import routine. I found some issues with it, and I just about have
    a patch to fix those items. I will open up a Jira issue once I get done.

    I really am interested in making EOModels work instead of Cayenne.xml,
    because I want to use WOBuilder and have the key completion work with
    EOGenericRecords. I will be building a WOCompatibility framework to address
    those needs. So if anyone has any ideas about what I should add please let
    me know.

    Thanks
    Garry
    On 5/12/06 6:00 PM, "Andrus Adamchik" wrote:

    On May 12, 2006, at 2:39 PM, Mike Kienenberger wrote:
    On 5/12/06, Watkins, Garry wrote:
    I am using NestedECs a bunch, is Cayenne's nested dataContext
    working
    yet?
    I think so, but Andrus would know for sure.
    Yep, nested DataContexts are fully supported.

    Does Cayenne have an EOGenericRecord equivalent yet?
    Yes, but I don't know if it's been seriously tested yet.
    Still it should work ok, as a generic record in Cayenne is just a
    CayenneDataObject, same as used as a common superclass already.

    Can I just use a .eomodeld instead of a cayenne.xml?
    No, but the modeler can read it in and save it back out as
    cayenne.xml.
    Theoretically you can customize the runtime to load an EOModel
    directly ... although there may be some issues converting inheritance
    and fetch specs, so you' probably want to import the EOModel in the
    Modeler, fix anything that doesn't look right, and then save as a
    Cayenne project.

    Andrus
    --
    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.
  • Andrus Adamchik at May 16, 2006 at 8:18 pm
    Actually we are going to get rid of DerivedDbAttribute past 1.2.
    Right now you may try to change the DbAttribute "name" property with
    the full column definition (haven't tried that myself - not sure
    whether this works or not), but in the next major release it looks
    like we need to add a "definition" property to DbAttribute.

    Andrus

    On May 14, 2006, at 5:22 PM, Watkins, Garry wrote:

    How does Cayenne support derived columns (from an EOModel) in a
    DbEntity? I
    am working on the import of an EOModel derived column formula, and it
    appears that my import is good.

    However, it looks like Cayenne Modeler does not support a
    DerivedDbAttribute
    in a regular DbEntity? Is that true? Does the framework support that
    combination? If that is true, then I won't worry about the modeler
    GUI not
    showing it correctly.

    This is what I have from the EOModel plist for the attribute:

    attributes = (
    {
    allowsNull = Y;
    definition = "dbo.years_diff(tsDateOfBirth, tsDateOfDeath,
    GETDATE())";
    name = age;
    valueClassName = NSNumber;
    valueType = l;
    }, ...)

    I create a DbDerivedAttribute called AGE, with the definition is
    the spec.

    Thanks
    Garry

    On 5/14/06 1:45 PM, "Watkins, Garry" wrote:

    Thanks Andrus,

    I am going to try and help you guys out again. It has been over a
    year
    since I contributed anything. Any way, I am currently working on the
    EOModel import routine. I found some issues with it, and I just
    about have
    a patch to fix those items. I will open up a Jira issue once I
    get done.

    I really am interested in making EOModels work instead of
    Cayenne.xml,
    because I want to use WOBuilder and have the key completion work with
    EOGenericRecords. I will be building a WOCompatibility framework
    to address
    those needs. So if anyone has any ideas about what I should add
    please let
    me know.

    Thanks
    Garry
    On 5/12/06 6:00 PM, "Andrus Adamchik" wrote:

    On May 12, 2006, at 2:39 PM, Mike Kienenberger wrote:
    On 5/12/06, Watkins, Garry wrote:
    I am using NestedECs a bunch, is Cayenne's nested dataContext
    working
    yet?
    I think so, but Andrus would know for sure.
    Yep, nested DataContexts are fully supported.

    Does Cayenne have an EOGenericRecord equivalent yet?
    Yes, but I don't know if it's been seriously tested yet.
    Still it should work ok, as a generic record in Cayenne is just a
    CayenneDataObject, same as used as a common superclass already.

    Can I just use a .eomodeld instead of a cayenne.xml?
    No, but the modeler can read it in and save it back out as
    cayenne.xml.
    Theoretically you can customize the runtime to load an EOModel
    directly ... although there may be some issues converting
    inheritance
    and fetch specs, so you' probably want to import the EOModel in the
    Modeler, fix anything that doesn't look right, and then save as a
    Cayenne project.

    Andrus
    --
    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.


  • Andrus Adamchik at May 16, 2006 at 8:13 pm
    Hi Garry,

    Looking forward to your contributions. BTW, now that we are in Apache
    incubator, we need some paperwork that will cover your past and
    future contributions. Could you please fill in the Contributor
    License Agreement [1] and mail and/or fax it to the ASF? I was going
    to ask you about that anyways, but now seems like we have a good
    occasion :-)

    [1] http://apache.org/licenses/

    Andrus

    On May 14, 2006, at 1:45 PM, Watkins, Garry wrote:

    Thanks Andrus,

    I am going to try and help you guys out again. It has been over a
    year
    since I contributed anything. Any way, I am currently working on the
    EOModel import routine. I found some issues with it, and I just
    about have
    a patch to fix those items. I will open up a Jira issue once I get
    done.

    I really am interested in making EOModels work instead of Cayenne.xml,
    because I want to use WOBuilder and have the key completion work with
    EOGenericRecords. I will be building a WOCompatibility framework
    to address
    those needs. So if anyone has any ideas about what I should add
    please let
    me know.

    Thanks
    Garry
    On 5/12/06 6:00 PM, "Andrus Adamchik" wrote:

    On May 12, 2006, at 2:39 PM, Mike Kienenberger wrote:
    On 5/12/06, Watkins, Garry wrote:
    I am using NestedECs a bunch, is Cayenne's nested dataContext
    working
    yet?
    I think so, but Andrus would know for sure.
    Yep, nested DataContexts are fully supported.

    Does Cayenne have an EOGenericRecord equivalent yet?
    Yes, but I don't know if it's been seriously tested yet.
    Still it should work ok, as a generic record in Cayenne is just a
    CayenneDataObject, same as used as a common superclass already.

    Can I just use a .eomodeld instead of a cayenne.xml?
    No, but the modeler can read it in and save it back out as
    cayenne.xml.
    Theoretically you can customize the runtime to load an EOModel
    directly ... although there may be some issues converting inheritance
    and fetch specs, so you' probably want to import the EOModel in the
    Modeler, fix anything that doesn't look right, and then save as a
    Cayenne project.

    Andrus
    --
    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.


  • Mike Kienenberger at May 12, 2006 at 3:10 pm

    On 5/12/06, Watkins, Garry wrote:
    I have been running into some issues with WO/EO that have been driving me
    nuts lately, like giving me Object not available errors, for optional to one
    relationships.

    My question is "Could Cayenne be used as a near drop in replacement for
    Enterprise Objects within a WO app server?" I think if we could implement
    key value coding, then it would be fairly simple to port some wo apps.
    I started using Cayenne by porting my WO app to Cayenne. Most of the
    conversion is simple find-and-replace.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdev @
categoriescayenne
postedMay 12, '06 at 2:57p
activeMay 16, '06 at 8:18p
posts10
users4
websitecayenne.apache.org

People

Translate

site design / logo © 2022 Grokbase