Comments for Blog of Adam Warski http://www.warski.org/blog Java and JBoss related stuff Sun, 13 May 2012 11:59:43 +0000 hourly 1 http://wordpress.org/?v=3.3.2 Comment on Dependency injection discourages object-oriented programming? by Adam Warski http://www.warski.org/blog/2010/10/dependency-injection-discourages-object-oriented-programming/comment-page-1/#comment-3660 Adam Warski Sun, 13 May 2012 11:59:43 +0000 http://www.warski.org/blog/?p=272#comment-3660 IoC is step one: making sure that a class isn't responsible for creating its dependencies, but the dependencies are provided from outside. In other words: use constructor arguments ;). And it's perfectly usable in small projects. DI is a step further, providing e.g. auto-wiring, containers etc. True that it makes no sense for small things. IoC is step one: making sure that a class isn’t responsible for creating its dependencies, but the dependencies are provided from outside. In other words: use constructor arguments ;). And it’s perfectly usable in small projects.

DI is a step further, providing e.g. auto-wiring, containers etc. True that it makes no sense for small things.

]]> Comment on Dependency injection discourages object-oriented programming? by Saeed Neamati http://www.warski.org/blog/2010/10/dependency-injection-discourages-object-oriented-programming/comment-page-1/#comment-3658 Saeed Neamati Sat, 12 May 2012 09:23:09 +0000 http://www.warski.org/blog/?p=272#comment-3658 I think the most important problem of DI is that, it's not for small projects. If you use it in a small project (wrong place) then it becomes an anti-pattern rather than being helpful at all. Where you don't want to be extensible and dynamic, why should you use it? Another problem I have is that name of IoC. I never understand it. ;). DI is meaningful and you do "inject" something that the class is "dependent" upon. But Inversion of Control doesn't make sense to me at all. I think the most important problem of DI is that, it’s not for small projects. If you use it in a small project (wrong place) then it becomes an anti-pattern rather than being helpful at all. Where you don’t want to be extensible and dynamic, why should you use it?

Another problem I have is that name of IoC. I never understand it. ;). DI is meaningful and you do “inject” something that the class is “dependent” upon. But Inversion of Control doesn’t make sense to me at all.

]]> Comment on Frameworks vs Libraries as Inheritance vs Composition? by Adam Warski http://www.warski.org/blog/2012/04/frameworks-vs-libraries-as-inheritance-vs-composition/comment-page-1/#comment-3619 Adam Warski Fri, 27 Apr 2012 06:04:59 +0000 http://www.warski.org/blog/?p=570#comment-3619 Not really, you could have a framework where you pass in callbacks as parameters, I suppose. These callbacks could implement an interface, but otherwise be ordinary objects. Not really, you could have a framework where you pass in callbacks as parameters, I suppose. These callbacks could implement an interface, but otherwise be ordinary objects.

]]> Comment on Frameworks vs Libraries as Inheritance vs Composition? by Zbigniew Łukasiak http://www.warski.org/blog/2012/04/frameworks-vs-libraries-as-inheritance-vs-composition/comment-page-1/#comment-3618 Zbigniew Łukasiak Fri, 27 Apr 2012 05:47:57 +0000 http://www.warski.org/blog/?p=570#comment-3618 Doesn't the definition of Framework imply using inheritance? Even if not - then there must be a direct analogy - in Framework it is the Framework code that calls your code - just like in the Template Method pattern (involving inheritance). Some time ago I've written: http://perlalchemy.blogspot.com/2010/02/frameworks-are-framing-libraries-are.html Doesn’t the definition of Framework imply using inheritance? Even if not – then there must be a direct analogy – in Framework it is the Framework code that calls your code – just like in the Template Method pattern (involving inheritance).

Some time ago I’ve written: http://perlalchemy.blogspot.com/2010/02/frameworks-are-framing-libraries-are.html

]]> Comment on Frameworks vs Libraries as Inheritance vs Composition? by Wolfgang http://www.warski.org/blog/2012/04/frameworks-vs-libraries-as-inheritance-vs-composition/comment-page-1/#comment-3511 Wolfgang Tue, 17 Apr 2012 12:25:38 +0000 http://www.warski.org/blog/?p=570#comment-3511 Good point about reuse: frameworks do not scale from one to many frameworks. Another criterion for the decision between framework and library: state and/or lifecycle. If the lifecycle of an object is an important aspect, the object should be managed by a framework. The point of control should be in the framework, so that there is a defined order of execution. If on the other hand the functions can be used without restrictions on order or lifecycle stages, they should be put into a library. Good point about reuse: frameworks do not scale from one to many frameworks.

Another criterion for the decision between framework and library: state and/or lifecycle.

If the lifecycle of an object is an important aspect, the object should be managed by a framework. The point of control should be in the framework, so that there is a defined order of execution.

If on the other hand the functions can be used without restrictions on order or lifecycle stages, they should be put into a library.

]]> Comment on Envers bundled with JBoss AS 7.0.2! by Adam Warski http://www.warski.org/blog/2011/09/envers-bundled-with-jboss-as-7-0-2/comment-page-1/#comment-3497 Adam Warski Thu, 12 Apr 2012 18:53:25 +0000 http://www.warski.org/blog/?p=532#comment-3497 With Envers, you can only query for data from one entity at a time. With Envers, you can only query for data from one entity at a time.

]]> Comment on Envers bundled with JBoss AS 7.0.2! by Ben http://www.warski.org/blog/2011/09/envers-bundled-with-jboss-as-7-0-2/comment-page-1/#comment-3492 Ben Tue, 10 Apr 2012 20:06:16 +0000 http://www.warski.org/blog/?p=532#comment-3492 hi, I am using hibernate 4.0.1 envers, at present we have typed query (joining multiple entities and restriving sub set of attributes from each entity). I would like to know is there a away to write a query which will return data from multiple entities(using envers revisions). Thanks in advance, Benarjee hi,
I am using hibernate 4.0.1 envers, at present we have typed query (joining multiple entities and restriving sub set of attributes from each entity). I would like to know is there a away to write a query which will return data from multiple entities(using envers revisions).

Thanks in advance,
Benarjee

]]> Comment on Modules, modules, modules … by Adam Warski http://www.warski.org/blog/2011/08/modules-modules-modules/comment-page-1/#comment-3448 Adam Warski Fri, 24 Feb 2012 19:19:44 +0000 http://www.warski.org/blog/?p=499#comment-3448 DRY - yes, but in another sense (name repetition). Encapsulation - yes, but on a higher level (hiding code in one module from another). But is it a higher level? The mechanism is the same, but we don't hide code in a class, we hide whole classes. Litte classes -> little modules? I guess modularity in the sense I meant isn't secondary at all. Both are important in fact. Adam DRY – yes, but in another sense (name repetition).
Encapsulation – yes, but on a higher level (hiding code in one module from another). But is it a higher level? The mechanism is the same, but we don’t hide code in a class, we hide whole classes.
Litte classes -> little modules?

I guess modularity in the sense I meant isn’t secondary at all. Both are important in fact.

Adam

]]> Comment on Modules, modules, modules … by Tomasz Nazar http://www.warski.org/blog/2011/08/modules-modules-modules/comment-page-1/#comment-3445 Tomasz Nazar Fri, 24 Feb 2012 09:31:01 +0000 http://www.warski.org/blog/?p=499#comment-3445 Looks like I assumed some context of my conclusions, and mistaken modularity you're talking about.. I thought you're writing on primary focus of OO: modularity of classes (encapsulation, DRY, small fns, little classes).. .. and in fact you're speaking on packages, modules.. which is .. ehmm.. secondary. So excuse my noise here.. We could talk about OO though :-) Looks like I assumed some context of my conclusions, and mistaken modularity you’re talking about..

I thought you’re writing on primary focus of OO: modularity of classes (encapsulation, DRY, small fns, little classes)..

.. and in fact you’re speaking on packages, modules.. which is .. ehmm.. secondary.

So excuse my noise here..
We could talk about OO though :-)

]]> Comment on Modules, modules, modules … by Adam Warski http://www.warski.org/blog/2011/08/modules-modules-modules/comment-page-1/#comment-3444 Adam Warski Wed, 22 Feb 2012 20:31:28 +0000 http://www.warski.org/blog/?p=499#comment-3444 AOP is good for cross-cutting concernes. I don't think anybody uses it for mixins. Speaking of mixins, how do they solve the above mentioned problems? In fact the Cake Pattern uses mixins extensively (it's based on some properties of traits), and still it's very far from perfect. Adam AOP is good for cross-cutting concernes. I don’t think anybody uses it for mixins.

Speaking of mixins, how do they solve the above mentioned problems? In fact the Cake Pattern uses mixins extensively (it’s based on some properties of traits), and still it’s very far from perfect.

Adam

]]>