Skip to main content

Strategy pattern in Symfony2



I'm trying to build simple service for rendering various types of pages. Basic concept is having something like:







$somePageType = new PageType(...);

$this->get('page.service')->render($somePagetype);







...which would be designed as Strategy pattern . Page types would implement interface with render method and page.service would call it. The problem is I'd like to use Doctrine in page type classes. What are my options here? I'd like to avoid creating service for each of these classes. Is that even possible? Is it possible to make them container aware without being services? Possibly, in the future, some page type might need something more than only Doctrine, so I need to keep in mind also that.


Comments

  1. I'm assuming PageType is an example of a strategy class. In that case, you could inject the dependencies by the page.service and you wouldn't need to define the strategies as services.

    Each strategy probably depends on different objects and therefore I guess you could make them ContainerAware. Here's an example how to do it

    // This is the page.service class
    class MyPageService {

    public function render(PageTypeInterface $page_type) {
    $page_type->setContainer($this->container);

    // do stuff
    }
    }

    // This is the type strategy
    class MyStrategyType extends ContainerAware implements PageTypeInterface {
    // you can access the container after MyPageService has injected it.
    }


    So basically each strategy would extend ContainerAware and the page.service would inject the container.



    EDIT

    If all of your strategies are dependant on the same services, I'd inject them instead of the whole container.

    class MyPageService {

    public function render(PageTypeInterface $page_type) {
    $page_type->setService($this->container->get('my_service'));

    // do stuff
    }
    }

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?

Java Urban Myths

Along the line of C++ Urban Myths and Perl Myths : What are the Java Urban Myths? That is, the ideas and conceptions about Java that are common but have no actual roots in reality . As a Java programmer, what ideas held by your fellow Java programmers have you had to disprove so often that you've come to believe they all learned at the feet of the same drunk old story-teller? Ideally, you would express these myths in a single sentence, and include an explanation of why they are false.