First of all, isn't #1 & #2 delicately interlinked? Well, I agree on both points, but I'm kind of certain that there is no real way out of it.
Let's formulate it like this; This Hibernate framework is pretty cool way to do it, but can yoiu fix so that all these pesky Sessions that is all over the place is not in my code? And while you are at it, I don't like that I have to detach/attach objects, and yeah the equals seems all buggered up? Some so called frameworks claim to be non-intrusive, but I have not seen any actual application being de-Springified (remove Spring and make it work without Spring), so I don't buy the argument. The counter-argument (for Spring) is that you can use it to a very small extent, making the rollback easier/smoother. To that I say, Qi4j is very similar to that respect, it is possible to for instance only use "objects" (I.e. ObjectBuilder) and have a handicapped Qi4j doing some rudimentary injections. So, could it be that Spring's (and Hibernate) success is less of "non-intrusive" and more like that of a drug dealer (first one is free), where the ease-of-getting-addicted has a strong focus from those communities, and that we should learn from it. HowTo; Getting Addicted to Qi4j and never want to turn back. (Some editor feedback of better title requested.) Interesting thoughts! As for "Diet Qi4j"; Rickard and I discussed that option about 2 years ago, before/at we introduced the Layers/Modules application structure. The conclusion was that the effort would be too immense and with too low benefit. Now, when we know so much more, I think that was a wise move... -- Niclas On 12 Nov 2009 18:59, "Jacek Sokulski" <[email protected]> wrote: Hi, After playing with Qi4j for some time I have two remarks pertaining the adoption of Qi4j: 1. It requires change of mind set while designing/programming, it can take some time, but I think it is a change in a good direction, so probable it is not so big issue 2. Qi4j seems to be a very strongly lock-in solution and this IS a big issue. If I use a library or framework I can usually encapsulate it, but Qi4j goes very deeply into application logic, it is more like using a new language. Any thoughts on this? A way of gradual adoption, maybe some Qi4j-light. A way/tool to back out? Jacek _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
