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)"
<[EMAIL PROTECTED]> 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 [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 12, 2006 10:57 AM
> To: [email protected]
> 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.
