Embedded resources are just another option people have. I've worked on projects with 40 tables and 40 sql map xml files. Its a pain to track down the one or two files that changed and remember to promote those. With embedded resource, everything gets packaged and promoted in one swoop.
--- Jeremy Gray <[EMAIL PROTECTED]> wrote: > Good day all. My name is Jeremy Gray, currently a contractor with > Siberra Digital Media Systems in Vancouver, Canada. We have been > evaluating ibatis.net for use in a number of our projects and the > results so far have been very promising indeed. We are also actively > monitoring a number of other frameworks such as Spring.Net, which I > mention for reasons that will soon become obvious. > > Though I am far from being in a position to more actively contribute > to > this mailing list, let alone the actual development project, at this > time, I have been monitoring the traffic and wanted to provide one > user's perspective in an area where I am repeatedly surprised by the > preferences expressed by developers (and users) of tools like ibatis > (and spring)... > > -----Original Message----- > From: Roberto Rabe (JIRA) [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 25, 2005 10:46 PM > To: ibatis-dev@incubator.apache.org > Subject: [jira] Commented: (IBATISNET-74) Improvement for > configuration > > --snip-- > > Otherwise, +1 for resource and embedded! > > -1 > > One of a laundry list of attractions to ibatis is the removal of > query > logic from our code without necessarily resorting to stored > procedures. > Use of embedded resources, however, directly defeats this. Such > resources must be compiled and, in an environment like the one in > which > I am currently contracting, a build triggers a whole series of work > items that a modification to a configuration file do not. > > The list of work items include but are not limited to the following: > issue tracking, branching, versioning, packaging, integration > testing, > regression testing, quality assurance sign-off, change/configuration > management, dependency management, release planning, etc. A number of > these are scaled back upon investigation but at the very least are > started up. > > A modification to a file that does not trigger a code build, while > still > having to go through some of these steps, goes through a much smaller > number thereof, and is much easier to escalate to a "production > hotfix", > hence the preference of external files over embedded resources. > > Having worked on a variety of projects over the years, I can > certainly > understand that there are applications out there where embedded > resources are more attractive for a number of reasons, but I am > somewhat > surprised at the apparent proportion of ibatis (and spring) users > that > seem enamored with embedded resources. > > Since the build->deployment processes here aren't exactly abnormally > formal, I expect that the interest in embedded resources comments > more > on the current users of ibatis than on this environment and thought I > might take a few minutes to chime in from the flipside. :) > > Jeremy Gray > Senior Software Developer > Siberra Digital Media Systems Corp. > >
