zendframework / zend-servicemanager-di

zend-di <-> zend-servicemanager integration

zend-servicemanager-di

Repository abandoned 2019-12-31

This repository has moved to laminas/laminas-servicemanager-di.

Provides integration for zend-di within zend-servicemanager

• File issues at https://github.com/zendframework/zend-servicemanager-di/issues
• Documentation is at https://docs.zendframework.com/zend-servicemanager-di/

zend-servicemanager-di's Issues

Provide support for PHP 7.2

We should not allow PHP 7.2 tests to fail.

We can remove support for HHVM.

Uncaught TypeError: Argument 2 passed to Zend\ServiceManager\Di\DiServiceFactory::get()

I'm using Zend\ServiceManager\Di\DiAbstractServiceFactory to create objects and it causes the fatal error:
Fatal error: Uncaught TypeError: Argument 2 passed to Zend\ServiceManager\Di\DiServiceFactory::get() must be of the type array, null given.

The issue related to incorrect implementation of \Zend\ServiceManager\Di\DiServiceFactory::get. As default parameter it uses an empty array but other methods can call it with null.

do not work

Example application: https://github.com/bupy7/zf3-sm-di

zend-servicemanager-di is not work.

Download application and run the application: composer serve

Error list:

1. Create new instance of controller via DI: http://localhost::8080 - ERROR
2. Create new instance of service via DI: http://localhost:8080/testservice - ERROR
3. Invalid class name for Container Interop. You can see my fix in Application/Module:19-21 line
4. Zend\ServiceManager\Di\DiAbstractServiceFactory was initialized double. Screenshot var_dump https://drive.google.com/open?id=0B9GZdWo-fVk0SkxGemo3Z1dzMUk . Code in Application/Module.

In ZF2 it all worked.

Change link to documentation in description

Please change link to docs in the repo description to docs.zendframework.com

DiAbstractServiceFactory Recursion

• I was not able to find an open or closed issue matching what I'm seeing.
• This is not a question. (Questions should be asked on chat (Signup here) or our forums.)

The Zend\ServiceManager\Di\DiAbstractServiceFactory when used as an abstract factory is causing recursion.

The issue is caused by Zend\ServiceManager\ServiceManager::has() function implementation and Zend\ServiceManager\Di\DiAbstractServiceFactoryFactory: :__invoke() function which is using DiAbstractServiceFactory::USE_SL_BEFORE_DI and Zend\ServiceManager\Di\DiServiceFactory: :get() method which is sending the object initialization request back to the Zend\ServiceManager\ServiceManager and as a result creating the recursion.

During object initialization by ServiceManager via DiAbstractServiceFactory the DiServiceFactory::get() method checks whether it should call ServiceManager (Service Locator) first by the following code (line 126) and therefore sends the object initialization request back to the ServiceManager because both conditions for the if statement are correct in this situation.

// Allow this di service to get dependencies from the service locator BEFORE trying DI.
if ($this->useContainer === self::USE_SL_BEFORE_DI && $this->container->has($name)) {    
     return $this->container->get($name);
 }

As the object initialization request is sent or pushed back to the ServiceManager and the ServiceManager will forward the request again to DiAbstractServiceFactory therefore creating the recursion (sending the request back and forth) and the end result is system memory exhausted.

Code to reproduce the issue

Please just use Zend\ServiceManager\Di\DiAbstractServiceFactory as an abstract factory
and then use ServiceManager to get/initialize an object. This object should not have any other factory class defined in the config. The only factory which should initialize this object should be Zend\ServiceManager\Di\DiAbstractServiceFactory.

Expected results

No Recursion.

Actual results

Recursion

Disable the repo wiki

Since the docs are located elsewhere this repo's empty wiki should be disabled.