Comments for Softaria http://softaria.com the software development company Fri, 04 May 2012 03:26:32 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on Our technology stack for web applications by Nathan http://softaria.com/2011/07/25/our-technology-stack-for-web-applications/#comment-76 Nathan Fri, 04 May 2012 03:26:32 +0000 http://softaria.com/?p=339#comment-76 Hey Roman, Thanks for the reply! My email address was required to post the comment, but here it is again: nfdavenport( at )yahoo( dot )com I've had a little further success this past week and got a minimal setup working finally, but I still love to hear and tips, tricks, advice, snippets that you would care to share. Thanks again! Hey Roman,

Thanks for the reply! My email address was required to post the comment, but here it is again: nfdavenport( at )yahoo( dot )com

I’ve had a little further success this past week and got a minimal setup working finally, but I still love to hear and tips, tricks, advice, snippets that you would care to share.

Thanks again!

]]> Comment on Cassandra ORM by roman http://softaria.com/2011/07/18/cassandra-orm/#comment-75 roman Wed, 02 May 2012 11:07:32 +0000 http://softaria.com/?p=317#comment-75 I will give it to anybody with contact information. If someone will wish to complete it and make a public project from it (e.g. on github) it would be just fine. I will give it to anybody with contact information. If someone will wish to complete it and make a public project from it (e.g. on github) it would be just fine.

]]> Comment on Cassandra ORM by roman http://softaria.com/2011/07/18/cassandra-orm/#comment-74 roman Wed, 02 May 2012 11:05:26 +0000 http://softaria.com/?p=317#comment-74 Just give me some of your contacts and we will discuss this. Just give me some of your contacts and we will discuss this.

]]> Comment on EclipseLink versus Hibernate by roman http://softaria.com/2011/07/26/eclipselink-versus-hibernate/#comment-73 roman Wed, 02 May 2012 11:03:32 +0000 http://softaria.com/?p=351#comment-73 Well, we have used Data Nucleus with Google App Engine. It worked just fine. So, probably it does the same for rdbms as well. But would you move from one technology which works well to another which, as you hear, does the same? Or have you any special reasoning for such a switch? Well, we have used Data Nucleus with Google App Engine. It worked just fine.
So, probably it does the same for rdbms as well.
But would you move from one technology which works well to another which, as you hear, does the same? Or have you any special reasoning for such a switch?

]]> Comment on Our technology stack for web applications by roman http://softaria.com/2011/07/25/our-technology-stack-for-web-applications/#comment-72 roman Wed, 02 May 2012 10:59:32 +0000 http://softaria.com/?p=339#comment-72 Hi Nathan, Well if you would leave some of your contacts, I'd share something with you Hi Nathan,

Well if you would leave some of your contacts, I’d share something with you

]]> Comment on Our technology stack for web applications by Nathan http://softaria.com/2011/07/25/our-technology-stack-for-web-applications/#comment-71 Nathan Sun, 29 Apr 2012 04:27:18 +0000 http://softaria.com/?p=339#comment-71 We've spent a couple of weeks researching our technology stack for a new project. It looks like we match your stack almost exactly, although we haven't quite got to the UI. Even there we are planning an AJAX intensive web UI and maybe we should look into Google Web Toolkit. (we are more familiar with jQuery so far). We have used Spring MVC in the past but are new to EclipseLink and PostgreSQL. We are considering using JPA and Spring Data - JPA in conjuction with these two. I'd love more detail on your experience there. Or if you would, even share some of your entityManager configuration. I'd like to compare it with what I have scraped together from google the past few days. Thanks for sharing what you've put together here already. We’ve spent a couple of weeks researching our technology stack for a new project. It looks like we match your stack almost exactly, although we haven’t quite got to the UI. Even there we are planning an AJAX intensive web UI and maybe we should look into Google Web Toolkit. (we are more familiar with jQuery so far).

We have used Spring MVC in the past but are new to EclipseLink and PostgreSQL. We are considering using JPA and Spring Data – JPA in conjuction with these two. I’d love more detail on your experience there. Or if you would, even share some of your entityManager configuration. I’d like to compare it with what I have scraped together from google the past few days.

Thanks for sharing what you’ve put together here already.

]]> Comment on EclipseLink versus Hibernate by Andy http://softaria.com/2011/07/26/eclipselink-versus-hibernate/#comment-70 Andy Mon, 16 Apr 2012 09:33:41 +0000 http://softaria.com/?p=351#comment-70 Some useful metrics, but not exactly thought through. If you are using JPA and using "extended" persistence context then you can obviously lazy load after a transaction is committed ... with any JPA implementation ... if they follow the JPA spec that is! DataNucleus JPA certainly allows that (since it still has the EntityManager and hence access to the connection pool). If using a "transaction" persistence context then all objects are <b>detached</b> at commit of the transaction hence they are not connected in any way to the persistence process and hence no lazy loading is going to happen. If you want to look at numbers of bugs and blockers, DataNucleus is shown here http://www.datanucleus.org/servlet/jira/secure/Dashboard.jspa It has far far fewer (even by adding all of the DataNucleus subprojects) than either of your other two options FWIW. That may be a sign of far more active developer action, or less usage ... but it started in 2003 building on the codebase of a project started in 2001). One thing is for sure, it gives far more predictable behaviour on all clients systems than the implementation(s) they used before trying it. As ever, try for yourself rather than believing claims, and make your own mind up Some useful metrics, but not exactly thought through.

If you are using JPA and using “extended” persistence context then you can obviously lazy load after a transaction is committed … with any JPA implementation … if they follow the JPA spec that is! DataNucleus JPA certainly allows that (since it still has the EntityManager and hence access to the connection pool). If using a “transaction” persistence context then all objects are detached at commit of the transaction hence they are not connected in any way to the persistence process and hence no lazy loading is going to happen.

If you want to look at numbers of bugs and blockers, DataNucleus is shown here http://www.datanucleus.org/servlet/jira/secure/Dashboard.jspa
It has far far fewer (even by adding all of the DataNucleus subprojects) than either of your other two options FWIW. That may be a sign of far more active developer action, or less usage … but it started in 2003 building on the codebase of a project started in 2001). One thing is for sure, it gives far more predictable behaviour on all clients systems than the implementation(s) they used before trying it. As ever, try for yourself rather than believing claims, and make your own mind up

]]> Comment on Cassandra ORM by Avishay Ben Natan http://softaria.com/2011/07/18/cassandra-orm/#comment-68 Avishay Ben Natan Tue, 24 Jan 2012 07:02:51 +0000 http://softaria.com/?p=317#comment-68 Hi Can we get the source code too? Hi
Can we get the source code too?

]]> Comment on Cassandra ORM by Matthew Tschiegg http://softaria.com/2011/07/18/cassandra-orm/#comment-58 Matthew Tschiegg Sun, 11 Dec 2011 02:56:10 +0000 http://softaria.com/?p=317#comment-58 I too would be interested in seeing it. You should post it on Github. I too would be interested in seeing it. You should post it on Github.

]]> Comment on Cassandra ORM by roman http://softaria.com/2011/07/18/cassandra-orm/#comment-30 roman Wed, 23 Nov 2011 15:51:03 +0000 http://softaria.com/?p=317#comment-30 In fact, I can send you source code (without any warranties) of course. Where should I send it? In fact, I can send you source code (without any warranties) of course.
Where should I send it?

]]>