tag:blogger.com,1999:blog-6979374.post109640430296171192..comments2023-06-22T09:08:08.066-04:00Comments on Seeking enlightenment...: Someone convince me about SpringWayland Chanhttp://www.blogger.com/profile/02746374187586611338noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-6979374.post-1130709457763528892005-10-30T16:57:00.000-05:002005-10-30T16:57:00.000-05:00SignatureSignatureAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6979374.post-1096439355126149002004-09-29T02:29:00.000-04:002004-09-29T02:29:00.000-04:00At the moment I'm doing some consulting at a big c...At the moment I'm doing some consulting at a big corporate and you're right, they're all using Oracle so there's no real need to be all pluggable and stuff. One of the architects here is heavily trying to prevent Spring from coming into the development team.<br /><br />A couple of days ago there was this developer that had huge problems with connections leeking all over the place. He got crazy Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6979374.post-1096426913290825552004-09-28T23:01:00.000-04:002004-09-28T23:01:00.000-04:00Spring's IoC container is quite powerful--it can u...Spring's IoC container is quite powerful--it can used consistently as THE solution for configuring and connecting your application objects in potenially any deployment environment (for example: web, system test, standalone, rich client, etc.) This capability greatly simplifies your application objects, as they are freed from having to configure and and manage their dependencies themselves (for Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6979374.post-1096420029853974032004-09-28T21:07:00.000-04:002004-09-28T21:07:00.000-04:00"Your first poing has nothing to do with the frame..."Your first poing has nothing to do with the framework. It's just the formalization of a good practice (coding to Interfaces) to begin with. As Rod essentially says in his book, this is simply recognizing a Design Pattern as a Best Practice."<br /><br />I don't agree. The spring framework (through IoC) isolates the layers of an application. If you don't use the Spring framework, you'll need Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6979374.post-1096410151242637292004-09-28T18:22:00.000-04:002004-09-28T18:22:00.000-04:00The "switch your database" argument is a weak one,...The "switch your database" argument is a weak one, to be sure. But that's just an absurd example of a more practical thing Spring enables: loose-coupling. When the components that make up your class are loosely-coupled, you can swap out implementations easily without impacting the code that depends on them. I'm not *necessarily* talking about databases here. A practical day-to-day swap you might Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6979374.post-1096410091779962412004-09-28T18:21:00.000-04:002004-09-28T18:21:00.000-04:00Your first poing has nothing to do with the framew...Your first poing has nothing to do with the framework. It's just the formalization of a good practice (coding to Interfaces) to begin with. As Rod essentially says in his book, this is simply recognizing a Design Pattern as a Best Practice.<br /><br />I do concede on your second point as I can see the wisdom in abstracting all the transaction coding away from your business logic and letting Wayland Chanhttps://www.blogger.com/profile/02746374187586611338noreply@blogger.comtag:blogger.com,1999:blog-6979374.post-1096407589531610842004-09-28T17:39:00.000-04:002004-09-28T17:39:00.000-04:00The 2 things I like about Spring have nothing to d...The 2 things I like about Spring have nothing to do with "magically switching databases".<br /><br />1. It lets me easily separate the UI/Business Logic/Data Access tiers of the application using interfaces. Sure, I could have written my own factory framework or some other way of doing it, but why reinvent the wheel.<br /><br />2. It handles opening/closing and transaction management for me soAnonymousnoreply@blogger.com