I guess this needs more clarification, but in short - keep using
DataContext if you were using it before.
Initial motivation for ObjectContext was that DataContext wasn't
flexible enough (i.e. had direct dependencies on DataDomain and even
DataNode) to work the same way in the app server tier and Java client
tier connecting to Cayenne web service. So ObjectContext was designed
to address that (and intentionally made an interface).
There is already a decent tier-agnostic implementation
(CayenneContext). However it is mostly useful on the client, as
wiring it to the current access stack is still somewhat arcane. I am
not (yet?) talking about migrating away from DataContext. Instead I
am looking into making DataContext one of ObjectContext implementations.
Looks like developers of traditional web application won't get the
taste of the new API until context nesting is implemented. I am
planning to look at it in the nearest future.
Client example of ObjectContext (and Cayenne Web Service) only exists
in CVS:
http://objectstyle.org/confluence/display/CAY/Multi+Tier+Examples
really straightforward...
Andrus
On Nov 7, 2005, at 10:36 PM, Geoff Hopson wrote:
> Also, as a noob, should I be using ObjectContext in place of
> DataContext?
>
> Any examples or sample code around as well?
>
> Ta
> Geoff
>
>
> On 07/11/05, Eric Schneider <eri..entralparksoftware.com> wrote:
> Andrus,
>
> Here's where I'm guilty again for half-paying attention.
> ObjectContext? Is this an eventual replacement for the DataContext
> all together?
>
> Thanks!
> eric
>
> On Nov 7, 2005, at 1:56 PM, Andrus Adamchik wrote:
>
> > Hi there. I just posted an M7 release. Please check out this blog
> > entry - there is lots of good stuff (though some of it is rather
> > specific):
> >
> > http://objectstyle.org/confluence/display/CAY/2005/11/07/
> >
> > Andrus
> >
> >
>
>
This archive was generated by hypermail 2.0.0 : Mon Nov 07 2005 - 15:38:43 EST