> JavaBeans?! Isn't that that horribly bloaty standard that everyone tells me > to avoid?
We support any class that Hibernate supports -- in other words, everything except constructor injection. We will eventually support constructor injection too though. And yes, iBATIS supports JavaBeans properties. And yes JavaBeans is an ugly, disgusting standard (your not alone in thinking that). But with that complaint, you need to go post on Sun's message board, not here. Cheers, Clinton On 8/9/07, Jonathan Alvarsson <[EMAIL PROTECTED]> wrote: > Hi I have been working a bit with Hibernate and want to get a look at > iBatis. I have read the first 80-90 pages of the "iBatis in action" book and > I am a bit confused. > > JavaBeans?! Isn't that that horribly bloaty standard that everyone tells me > to avoid? What's it doing in what I thought was a lightweight and easy > framework? > > I read that iBatis doesn't make any demands on the domain model. Then the > book says that I should use JavaBeans and mumbles something about a 114 > pages specification and starts to tell me about the most basic stuffs about > JavaBeans and more or less hints that this will not be enough. I feel > somewhat confused now. Isn't this a demand on the domain model? > > Please explain this because it just doesn't make sence to me... > > -- > // Jonathan
