Hi All, While the tone of the emails does sound in favor of EOF, could you please share some concrete instances and examples of why Hibernate doesn't cut it for you?
Some of the aspects about Hibernate that I thought were different than EOF [in a good way] 1. the Session doesn't need to be tightly bound. unlike EOEditingContext that's tightly bound to the EOObjectStoreCoordinator 2. it's easier to multi-thread and connection pool with Hibernate 3. Hibernate validators are not too bad for basic validations Thanks, Karthik On Wed, Feb 25, 2009 at 4:38 AM, Oliver Scheel <[email protected]> wrote: > > > I'm not really a good friedn of hibernate, at last semester of school I > tried to propose the teacher to learn WO-EOF instead, he was about to put 0 > on my grade, :S. hehehe. I really don't like to put @anotations at the > begining of classes and methods, but well probably thats out of topic. > > > though annotations are a nice feature for some stuff, but to define the OR > mapping...argh! The same mistake in EJB 3.0... > > Oliver > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > > http://lists.apple.com/mailman/options/webobjects-dev/karthik.nar%40gmail.com > > This email sent to [email protected] >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
