oop - What are the known "gotchas" with regards to the Chain of Responsibilty pattern? -

I'm often using patterns in my current project (3 times often for me) and I'm wondering if I I'm quite excited about the solution, especially, I am using Apache Commons, so far I've been impressed so much that it has simplified many complex interchangeable pieces of app logic into a more compositor and organized whole is. However, some of the new people on this project "have difficulty finding it." What are your experiences with this? What problems did you face in its implementation?

So far, I have only seen one problem that when you are trying to deal with the items that need to be closed when you complete the execution of your chain then stored in your reference category He makes those objects for a pain. I was able to work around using filters instead of commands, but it seems that this is a little unknown because your close statements are often far from the object from which the object was immediately made.

Anyway, I would love to hear

"post-text" itemprop = "text"

<> P> I have to say that it works well for the unspecific problem (such as framework mode) but works very little specific problem framework other people , And you want to give the full freedom of implementation to the customer. Once you know what you are going to do to solve the problem, then I think the other solutions are better.

The risk of chain of responsibility patterns is similar to the blackboard pattern; It is actually very easy that the price has not been provided in the final goal. Order objects and processing objects actually make the argument of your application, and you're hiding it behind a processing chain, where your most important code is. It is very easy to understand and maintain if you only process one method (or several methods) which represent the complete processing chain without the period of the processing chain. The processing chain can actually hide the business logic of your application, and I think that you prefer technical artifacts to business code.

So basically you replace it may be very straight-forward application code that read is very easy with very intuitive processing chains You are doing meta programming privately, I have never met any meta-programming at all, so I agree with those affiliates who dislike it;)