This is outside the scope of the iBATIS discussion, but why wouldn't you consider using Spring for your application? I've written several non-web-based apps using Spring and can say it simplified the development and configuration of the app, plus, it gives you intrinsic access to a ton of resources, such as iBATIS, out-of-the-box. Unless you've already started heavy development without Spring, it wouldn't be a terrible effort to add it.
-Ryan On Sun, Mar 2, 2008 at 11:09 AM, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > Hello, > > I am a student (college university) working on a part of a fictive project > management software system. > > We received a database dll scheme, so Hibernate was not really an option. > It's also a very short project (8 weeks) so iBATIS is definitely a better > solution. > (shorter learning curve) > > I've bought iBATIS in action and generated Java Beans and sqlmaps with > abator. > > But now I am stuck. I need some sort of Factory/Facade/Controller for the > sqlMaps, but how to code these? > It's a desktop app, so isn't the (Spring) DAO overkill??? (I also don't > have enough time...) > Is it necessary to use a DAO? Is the iBATIS DAO out-of-date because it > isn't under development anymore? > > I don't like the MVC solution we've seen in the Java lessons - manually > writing a Connection class, and Mapper classes (Prepared and Callable > statements) > ...but I also don't really know how to fill in the gap between Swing > (view) and the sqlmaps + beans... > > Any help is greatly appreciated. > > A desperate ;-) student > Greeting, PieterB > > > > >
