On Wed, Apr 8, 2009 at 1:30 PM, David Holt <[email protected]> wrote:
> I found this little snippet from way back in 03: > > Damon Clinkscales's "Object Persistence Approaches" presentation further > compared JDO and EJB with WebObjects's Enterprise Objects Framework (EOF). > EOF is a third-party object persistence framework library owned by Apple and > provides the technology behind the Apple e-commerce Website. Since EOF is a > pure Java library, it does not require complex containers (EJB) or byte code > post-processors (JDO). EOF provides access to the generated raw SQL, and > adaptors can provide access to nonrelational datastores. However, EOF is a > nonstandard vendor-specific technology. It requires the developer to learn > the proprietary API and creates vendor lock-in. > > http://www.javaworld.com/javaworld/jw-03-2003/jw-0314-nfjs.html?page=3 > > So it sounds like a specific adaptor will have to be created for the Google > Datastore? > The blog associated with the new Google App Java feature contained this one entry today: Thomas Mueller View profile <goog_1239233844236> <goog_1239233844236> <goog_1239233844236>More options <goog_1239233844236> <goog_1239233844236>Apr 8, 4:52 pm<goog_1239233844236> Java Database Connectivity (JDBC): "Not supported" is technically not correct. Better would be: "Not supported by Google". Reason: the APIs are there, and using third-party in-memory databases such as the H2 Database Engine (which I write) or HSQLDB work. I plan to write an open souce datastore to JDBC wrapper so that people can use the JDBC API directly via frameworks that use the JDBC API.
_______________________________________________ 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]
