Ye I see, but would not it be better if Doctrine* modules would be dependable
only on ModuleManger/ServiceProvicer but without MVC? As of me, I setup this
way, for now it looks like it works:
$listener = new ListenerOptions();
$moduleManager = new ModuleManager();
$serviceManager = new ServiceManager();
/**
* Includes ConfigListener, ModuleAutoloader, AutoloaderListener,
ModuleResolverListener
* and others are my own need listeners.
*/
$moduleManager->getEventManager()->attachAggregate(new MyOwnAggregator());
$serviceManager->setService('Configuration',
$moduleManager->getEvent()->getConfigListener()->getMergedConfig(false));
$serviceManager->setAlias('Config', 'Configuration');
$moduleManager->getModule('DoctrineModule')->init($moduleManager);
$moduleManager->getModule('DoctrineORMModule')->init($moduleManager);
$serviceManager->get('Doctrine\ORM\EntityManager')
Marco Pivetta wrote
> The ORM module expects an MVC-ish setup, so that's the correct way of
> instantiating everything. That's also the way I setup functional tests in
> my test environment (see https://gist.github.com/Ocramius/3994325 )
>
> Marco Pivetta
>
> http://twitter.com/Ocramius
>
> http://ocramius.github.com/
>
>
> On 27 February 2013 15:51, Deserved [via Zend Framework Community] <
> [email protected]
>> wrote:
>
>> Marco Thank You for your instant reply, your solution works but it has to
>> many things that I am not gonna need. Anyway it helped me to identify
>> what
>> exactly I am missing. It was 'Configuration' Service, that is looks like
>> eventually a pointer to ListenerOption, and 'Config' that is alias to
>> 'Configuration' and it works aswell :)
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://zend-framework-community.634137.n4.nabble.com/Doctrine-2-module-is-tight-to-MVC-tp4659346p4659352.html
>> To start a new topic under Zend Framework, email
>>
> [email protected]
>> To unsubscribe from Zend Framework Community, click
>> here<http://zend-framework-community.634137.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=634137&code=b2NyYW1pdXNAZ21haWwuY29tfDYzNDEzN3wxNzE0OTI1MTk4>
>> .
>> NAML<http://zend-framework-community.634137.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
--
View this message in context:
http://zend-framework-community.634137.n4.nabble.com/Doctrine-2-module-is-tight-to-MVC-tp4659346p4659356.html
Sent from the Zend Framework mailing list archive at Nabble.com.
--
List: [email protected]
Info: http://framework.zend.com/archives
Unsubscribe: [email protected]
