As a follow-up to my previous post I have run across a dead project called "O/R Broker" that does exactly what I am looking for. It allows one to query and persist non-JavaBeans objects using constructor- injection. Please see http://orbroker.sourceforge.net/ and http://orbroker.sourceforge.net/documentation/user-guide.shtml
I don't see anything stopping us from applying the same techniques in JPA. If I understand correctly, all we'd need to do is annotate constructor parameters using @Column to indicate what database column should go into each parameter. That seems simple enough. What do you think? Gili On Feb 25, 12:24 am, Gili Tzabari <[email protected]> wrote: > Remind me to shoot the person who first came up with the idea of > using XML for human-edited configuration files... > > Speaking of using ORMs with Guice, do you suppose it is technically > possible to use constructor-injection with ORMs instead of the JavaBeans > model that has become the norm? In my experience the latter leads to > very bad API designs. > > Gili > > Praveena Manvi wrote: > > I guess the question which persistence technology is better suited to > > take maximum advantage of Guice? > > I guess JPA is already mature in terms of using annotation & dependcy > > injection. There is lot of scope for using the same for iBatis, BTW > > Clinton Begin > > <http://www.nofluffjuststuff.com/speaker_view.jsp?speakerId=212> > > (Author of iBatis) never liked the idea of Java5/Generics etc.. :) > > > As pointed out rightly from Rick "Guice" cannot be used for deciding > > on which persistence technique to use. > > > Rick-> Could you please help us to understand how Guice was used with > > iBatis (if you have integrated both). > > > On Wed, Feb 25, 2009 at 9:26 AM, Rick <[email protected] > > <mailto:[email protected]>> wrote: > > > On Tue, Feb 24, 2009 at 10:33 PM, Seto <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hibernate?iBatis?Some other object dbs like db4o? > > > What could take full advantage with guice? > > > Could someone give me some suggestions? > > > I wouldn't make my ORM(hibernate/JPA) or SQLMapping(ibatis) decision > > based AT ALL in regard to guice. Guice will help a bit with whatever > > you choose (I'm using guice now with iBATIS), but definitely don't > > base your persistence decision based on guice integration. > > > The decision of what type of persistence layer to use should be based > > on a lot of other factors. Obviously this isn't the forum for a > > discussion on persistence layer choices, but I tend to give the advice > > of... > > > If you have to work with a legacy database that is quite large and has > > a lot of join tables, I always suggest iBATIS. If it's a brand new > > application where the database can evolve with the development of your > > application, an ORM solution like Hibernate should be fine. I still > > have a bias towards iBATIS in either case, but I'm not really bigoted > > to much one way or the other and they really aren't 'true' competing > > technologies (iBATIS doesn't claim to be an ORM solution.) > > > -- > > Rick R > > > -- > > “One never finds life worth living, one always has to make it worth > > living.” > > —Rev. Harry Emerson Fosdick, D.D. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-guice?hl=en -~----------~----~----~----~------~----~------~--~---
