Comments on: Reviewing Google AppEngine for Java (Part 1) http://blog.newsplore.com/2009/05/27/reviewing-google-appengine-for-java-part-1 Everything beta Thu, 26 Jan 2012 21:31:17 +0000 hourly 1 http://wordpress.org/?v=3.3 By: conveyancing birmingham http://blog.newsplore.com/2009/05/27/reviewing-google-appengine-for-java-part-1/comment-page-1#comment-929 conveyancing birmingham Sat, 10 Sep 2011 11:26:00 +0000 http://blog.newsplore.com/?p=1093#comment-929 This is a nice content.I like this content.This is a nice content.I appreciate to this content.The written skill is so good.Thanks to share this blog.Keep sharing.  This is a nice content.I like this content.This is a nice content.I appreciate to this content.The written skill is so good.Thanks to share this blog.Keep sharing. 

]]> By: Jonathan Elano http://blog.newsplore.com/2009/05/27/reviewing-google-appengine-for-java-part-1/comment-page-1#comment-927 Jonathan Elano Wed, 24 Aug 2011 11:53:00 +0000 http://blog.newsplore.com/?p=1093#comment-927 Even without their discounts www.jvmhost.com seems to be the cheapest Java provider on the market. Even without their discounts http://www.jvmhost.com seems to be the cheapest Java provider on the market.

]]> By: excelmacrotraining http://blog.newsplore.com/2009/05/27/reviewing-google-appengine-for-java-part-1/comment-page-1#comment-925 excelmacrotraining Mon, 08 Aug 2011 06:40:00 +0000 http://blog.newsplore.com/?p=1093#comment-925 Somewhere along the way Hibernate showed us all how ORM should be done and it become so  very popular Thanks to share this blog.I really appreciate. Somewhere along the way Hibernate showed us all how ORM should be done and it become so  very popular Thanks to share this blog.I really appreciate.

]]> By: Florin http://blog.newsplore.com/2009/05/27/reviewing-google-appengine-for-java-part-1/comment-page-1#comment-307 Florin Thu, 18 Jun 2009 15:44:26 +0000 http://blog.newsplore.com/?p=1093#comment-307 Hi Matt, Here's the RSS feed URL: http://feeds.feedburner.com/EverythingBeta I added an RSS icon onthe top-right corner of the blog for better reach. Hi Matt,
Here’s the RSS feed URL: http://feeds.feedburner.com/EverythingBeta
I added an RSS icon onthe top-right corner of the blog for better reach.

]]> By: Matt http://blog.newsplore.com/2009/05/27/reviewing-google-appengine-for-java-part-1/comment-page-1#comment-295 Matt Tue, 16 Jun 2009 18:01:42 +0000 http://blog.newsplore.com/?p=1093#comment-295 Hello - I like your blog but cannot figure out how to subscribe to your feed. Do you have a feed url? -Thanks Hello – I like your blog but cannot figure out how to subscribe to your feed. Do you have a feed url? -Thanks

]]> By: Andy http://blog.newsplore.com/2009/05/27/reviewing-google-appengine-for-java-part-1/comment-page-1#comment-241 Andy Sat, 30 May 2009 05:15:40 +0000 http://blog.newsplore.com/?p=1093#comment-241 "Transparent bytecode enhancement" .... you mean what I already wrote "runtime enhancement", that DN already supports. OpenJPA supports the same post-compile and runtime options. Don't see you complaining about that. Heck EclipseLink also does. “Transparent bytecode enhancement” …. you mean what I already wrote “runtime enhancement”, that DN already supports. OpenJPA supports the same post-compile and runtime options. Don’t see you complaining about that. Heck EclipseLink also does.

]]> By: Florin http://blog.newsplore.com/2009/05/27/reviewing-google-appengine-for-java-part-1/comment-page-1#comment-239 Florin Fri, 29 May 2009 21:42:11 +0000 http://blog.newsplore.com/?p=1093#comment-239 <b>Transparent</b> bytecode enhancement is a common feature, explicit enhancement is not. With respect to AOP, if you refer to AspectJ, there's an option to do runtime bytecode enhancement as well as through a static precompilation step. SpringAOP doesn't require static bytecode enhancement (it uses dynamic proxying via either JDK proxies or CGLIB). But to *mandate* a precompilation step is a restriction of GAE+DN as it complicates the build and deployment. It's true, DN supports non-RDBMS stores and I've updated the post to reflect that. It's great to hear that it's been around from 2003 and it became "very popular". Somewhere along the way Hibernate showed us all how ORM should be done and it become so "very popular" that it's been adopted as a standard (after already being the de facto standard). Transparent bytecode enhancement is a common feature, explicit enhancement is not. With respect to AOP, if you refer to AspectJ, there’s an option to do runtime bytecode enhancement as well as through a static precompilation step. SpringAOP doesn’t require static bytecode enhancement (it uses dynamic proxying via either JDK proxies or CGLIB). But to *mandate* a precompilation step is a restriction of GAE+DN as it complicates the build and deployment.
It’s true, DN supports non-RDBMS stores and I’ve updated the post to reflect that. It’s great to hear that it’s been around from 2003 and it became “very popular”. Somewhere along the way Hibernate showed us all how ORM should be done and it become so “very popular” that it’s been adopted as a standard (after already being the de facto standard).

]]> By: Andy http://blog.newsplore.com/2009/05/27/reviewing-google-appengine-for-java-part-1/comment-page-1#comment-238 Andy Fri, 29 May 2009 14:23:54 +0000 http://blog.newsplore.com/?p=1093#comment-238 DataNucleus is a *wise* choice. It allows persistence to any type of datastore (LDAP, XML, ODF, Excel, ODBMS, RDBMS, BigTable, Hadoop, JSON), not just the limited type (RDBMS) allowed by Hibernate, EclipseLink, and OpenJPA. Just because *you* haven't heard of it before isn't a reason for anything. It has been around since 2003 (called JPOX) and is well enough known. In fact it's been "very popular" since 2004. Use of JDO makes plenty of sense on this datastore too. > DataNucleus JPA requires a pre-compilation step that does bytecode enhancement which I completely dislike as it’s archaic Check your facts. DataNucleus requires bytecode enhancement of classes. This is a common feature these days, present in anything AOP. It allows you to do this as part of compilation, as a post-compile step, or at runtime. Ant integration is in the our docs, as is the Maven integration, and the Eclipse integration, and the runtime enhancement. As ever, the DN forum would be a more suitable place if you have comments about it as a product, since its developers aren't going to come across your blog as a matter of course. DataNucleus is a *wise* choice. It allows persistence to any type of datastore (LDAP, XML, ODF, Excel, ODBMS, RDBMS, BigTable, Hadoop, JSON), not just the limited type (RDBMS) allowed by Hibernate, EclipseLink, and OpenJPA. Just because *you* haven’t heard of it before isn’t a reason for anything. It has been around since 2003 (called JPOX) and is well enough known. In fact it’s been “very popular” since 2004. Use of JDO makes plenty of sense on this datastore too.

> DataNucleus JPA requires a pre-compilation step that does bytecode enhancement which I completely dislike as it’s archaic

Check your facts. DataNucleus requires bytecode enhancement of classes. This is a common feature these days, present in anything AOP. It allows you to do this as part of compilation, as a post-compile step, or at runtime. Ant integration is in the our docs, as is the Maven integration, and the Eclipse integration, and the runtime enhancement.

As ever, the DN forum would be a more suitable place if you have comments about it as a product, since its developers aren’t going to come across your blog as a matter of course.

]]>