Symfony feature status

CON= TENT OF THIS PAGE IS UNDER REVIEW

For a eZ Publish 4.x vs 5.x comparison, see here.

All Symonfy features are essentially working also in eZ Publish 5; this = page describes features used out of the box however with limitations due to= the eZ Publish 5 features developed on top, and features not<= /u> used out of the box for a reason described here.

Limitation= s of eZ Publish 5 features:

Feature	Supported	Limitations
Configuration	All configuration uses standard ym= l configuration	Siteaccess (Semantic) configuration is something that has = been built on top of Symfony Standard Services do not support them They are not cached but lookup occurs based on cached Symfony configura= tion Unit tests currently use ini files and own configuration system
Dependency injection	Injection Supported for all services	See known issues (eg. missing possibility to inject Criterion) Unit tests currently use own dependency injection system driven by own = ini system
Security	Own Firewall voter that uses eZ Publish user rig= hts	eZ User is not the same as a Doctrine provided user Limitations do not apply at this stage but instead at data retrieval ti= me

Not used out of the box= :

Feature	Reason
Doctrine ORM	While the full ORM is not used out of the box, a= s of 5.3 we use Doctrine DBAL making it possible to share connection = and connection settings between eZ Publish and regular Doctrine ORM use.
Annotations	We don't currently bundle FrameworkExtraBundle w= hich provides support for Annotating routes/firewall rules on controllers a= nd other features. Workaround: customer can add it in composer and install = it like any other bundle.