And about the state of an object after you call
entityManager.persist(object) with Cayenne... can your offer any
insights?...I mean in what state is the object? NEW (as it should to be
consistent with Cayenne classic?) or COMMITTED? (to be consistent with JPA
as implemented by Hibernate)
Does it really need to be COMMITTED to be consistent with JPA? Or is this an
abstraction leak in JPA/Hibernate ?
Aristedes Maniatis wrote:
> On 12/03/2009, at 9:04 AM, Francisco Peredo wrote:
>> Hi!I really wonder why nobody has built something like Cayenne on
>> top of JPA,
>> I mean, it should be clear that Cayenne is higher level API that
>> offers a
>> lot of advantages..
> Andrus has already spent a vast amount of time on moving Cayenne
> toward JPA compliance. It is not a goal for 3.0 because other more
> important issues are being addressed first. Even though quite a lot of
> JPA already works, as you know with the JSR process, you can't be
> 'almost compliant'. Cayenne will only be able to be advertised as JPA
> compliant when all the tests pass.
> As for inheritance, Cayenne already supports single table inheritance
> and vertical/horizontal are probably only some months away.
> Finally, don't be scared by the 3.0M6 naming. It is certainly stable
> enough to be used in production, however there is no guarantee that
> the API is finalised. So if you use the milestone you may need to
> alter your code slightly for the next milestone.
> Level 1, 30 Wilson Street Newtown 2042 Australia
> phone +61 2 9550 5001 fax +61 2 9550 4001
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
-- View this message in context: http://www.nabble.com/Coming-from-EOF%3A-Cayenne-vs-Hibernate-tp22463349p22477651.html Sent from the Cayenne - User mailing list archive at Nabble.com.
This archive was generated by hypermail 2.0.0 : Thu Mar 12 2009 - 10:35:53 EDT