Comments for Relevance Found http://www.relevancefound.com Relevant ... Reliable ... Material Wed, 07 Jan 2009 09:43:32 +0000 http://wordpress.org/?v=abc hourly 1 Comment on CakePHP vs Django dilemma by Rapid development frameworks - CakePHP, Django, RoR - Relevance Found http://www.relevancefound.com/2008/11/cakephp-vs-django-dilemma/comment-page-1/#comment-9 Rapid development frameworks - CakePHP, Django, RoR - Relevance Found Fri, 26 Dec 2008 09:05:05 +0000 http://www.relevancefound.com/?p=13#comment-9 [...] izamryan on Dec.26, 2008, under Technology Last month I blogged about a comparing rapid development frameworks. These are tools that help you develop web-based applications. They provide building blocks of [...] [...] izamryan on Dec.26, 2008, under Technology Last month I blogged about a comparing rapid development frameworks. These are tools that help you develop web-based applications. They provide building blocks of [...]

]]> Comment on Score, for OSS, IBM and ADempiere by izamryan http://www.relevancefound.com/2008/12/score-for-oss-ibm-and-adempiere/comment-page-1/#comment-5 izamryan Wed, 03 Dec 2008 11:30:06 +0000 http://www.relevancefound.com/?p=19#comment-5 Hai Croo! :-) I see your point re: Spring & Entity EJBs. And I feel that the advantages of using POJOs hasn't been emphasised enough! Inversion of Control (IoC) techniques can help create elegant, clean, functional code. I've been playing around with CakePHP (and a little bit of Ruby on Rails), and I'm really beginning to appreciate IoC techniques. Well ... back to lurking in the ADempiere project forums ... Hai Croo! :-)
I see your point re: Spring & Entity EJBs. And I feel that the advantages of using POJOs hasn’t been emphasised enough! Inversion of Control (IoC) techniques can help create elegant, clean, functional code.

I’ve been playing around with CakePHP (and a little bit of Ruby on Rails), and I’m really beginning to appreciate IoC techniques.

Well … back to lurking in the ADempiere project forums …

]]> Comment on Score, for OSS, IBM and ADempiere by Colin Rooney http://www.relevancefound.com/2008/12/score-for-oss-ibm-and-adempiere/comment-page-1/#comment-4 Colin Rooney Wed, 03 Dec 2008 10:31:34 +0000 http://www.relevancefound.com/?p=19#comment-4 Hi Izamryan, I'm sure there will be lots of debate on the topic in the project forums and I will address this point there too, but I would take exception to the point that the Spring framework is a competitor in terms of persistence to Entity EJBs. Actually Spring has no persistence of its own and simple wraps the actually persistence. And it "wraps" it in the Spring Inversion-of-Control container... which is what Spring is really. A small, light and efficient IoC. Now for some reason the concept of IoC seems to be perplexing to many, but I think when one looks close it's actually a very simple yet clever idea. More in the Adempiere forums. To anyone that does believe Spring to include its own persistence I ask for an example? I think you'll find any example is simply wrapping jdbc, Hibernate, Toplink or EJB or some other persistence technology. Do you remember when SQL arrived on the scene first? It was going to standardise access to databases. In one sense it was a success but strange that we discuss in Adempiere (an application based on much SQL) the need for DB independence. Is SQL not a standard? To me Spring offers protection from that... protection that at some point Entity EJBs become non-standard or that we wish to move to a new persistence approach but the cost of rewriting all the EJB framework code embedded in our Business Logic is too much - much the same issue we in Adempiere face today with SQL, don't you think? Many find Spring complex. But actual I believe those people have failed to grasp the Inversion concept. There is a need to configure (in XML files) that is slightly more complex but then the reward is the business logic has zero (absolutely zero) framework code and you end up with plain old java objects (POJOs). This makes it easy for those not versed in the framework to write business logic witouy the need to understand EJBs, Hibernate, seam or any other framework! Of course Spring offers many other benefits and it's popularity I believe are making it (if it is not already) a "de facto" standard. Colin Hi Izamryan,

I’m sure there will be lots of debate on the topic in the project forums and I will address this point there too, but I would take exception to the point that the Spring framework is a competitor in terms of persistence to Entity EJBs. Actually Spring has no persistence of its own and simple wraps the actually persistence. And it “wraps” it in the Spring Inversion-of-Control container… which is what Spring is really. A small, light and efficient IoC. Now for some reason the concept of IoC seems to be perplexing to many, but I think when one looks close it’s actually a very simple yet clever idea. More in the Adempiere forums.

To anyone that does believe Spring to include its own persistence I ask for an example? I think you’ll find any example is simply wrapping jdbc, Hibernate, Toplink or EJB or some other persistence technology.

Do you remember when SQL arrived on the scene first? It was going to standardise access to databases. In one sense it was a success but strange that we discuss in Adempiere (an application based on much SQL) the need for DB independence. Is SQL not a standard? To me Spring offers protection from that… protection that at some point Entity EJBs become non-standard or that we wish to move to a new persistence approach but the cost of rewriting all the EJB framework code embedded in our Business Logic is too much - much the same issue we in Adempiere face today with SQL, don’t you think?

Many find Spring complex. But actual I believe those people have failed to grasp the Inversion concept. There is a need to configure (in XML files) that is slightly more complex but then the reward is the business logic has zero (absolutely zero) framework code and you end up with plain old java objects (POJOs). This makes it easy for those not versed in the framework to write business logic witouy the need to understand EJBs, Hibernate, seam or any other framework!

Of course Spring offers many other benefits and it’s popularity I believe are making it (if it is not already) a “de facto” standard.

Colin

]]>