Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doctrine orm service must be true by default #298

Closed
pdias opened this issue Dec 4, 2017 · 2 comments
Closed

Doctrine orm service must be true by default #298

pdias opened this issue Dec 4, 2017 · 2 comments

Comments

@pdias
Copy link
Contributor

pdias commented Dec 4, 2017

After update to SF3.4 i have this warning (if doctrine_integration is set to true in config, default is true):

User Deprecated: The "doctrine.orm.default_entity_manager" service is private, getting it from the container is deprecated since Symfony 3.2 and will fail in 4.0. You should either make the service public, or stop using the container directly and use dependency injection instead.

This warning is caused by the JMSDIExtraBundle proxy replacing the Doctrine service.

JMSDIExtraBundle, does not properly preserve the service visibility when overwriting the service.

Thanks,

Paulo Dias

pdias added a commit to pdias/JMSDiExtraBundle that referenced this issue Dec 4, 2017
Solves:

User Deprecated: The "doctrine.orm.default_entity_manager" service is private, getting it from the container is deprecated since Symfony 3.2 and will fail in 4.0. You should either make the service public, or stop using the container directly and use dependency injection instead.

This warning is caused by the JMSDIExtraBundle proxy replacing the Doctrine Service.
JMSDIExtraBundle, does not properly preserve the service visibility when overwriting the service.
@pdias pdias closed this as completed Dec 12, 2017
GuilhemN pushed a commit that referenced this issue Jan 12, 2018
* Solves #298

Solves:

User Deprecated: The "doctrine.orm.default_entity_manager" service is private, getting it from the container is deprecated since Symfony 3.2 and will fail in 4.0. You should either make the service public, or stop using the container directly and use dependency injection instead.

This warning is caused by the JMSDIExtraBundle proxy replacing the Doctrine Service.
JMSDIExtraBundle, does not properly preserve the service visibility when overwriting the service.

* Compatibility with older SF versions

Method isPrivate don't exist in Symfony\Component\DependencyInjection\DefinitionDecorator in versions prior to 2.3

* Compatibility with older SF versions 

Method isPrivate don't exist in Symfony\Component\DependencyInjection\DefinitionDecorator in versions prior to 2.3

* Compatibility with older SF versions

Method isPrivate don't exist in Symfony\Component\DependencyInjection\DefinitionDecorator in versions prior to 2.3
@ajtis
Copy link

ajtis commented Jan 12, 2018

@pdias please create new rel/tag.

@slawomirkania
Copy link

@pdias like above, please create tag

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants