You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using different components with Doctrine 2, you may end up with them using two different metadata drivers, for example, XML and YAML. You can use the DriverChain Metadata implementations to aggregate these drivers based on namespaces:
Based on the namespace of the entity the loading of entities is delegated to the appropriate driver. The chain semantics come from the fact that the driver loops through all namespaces and matches the entity class name against the namespace using a strpos() === 0 call. This means you need to order the drivers correctly if sub-namespaces use different metadata driver implementations.
The text was updated successfully, but these errors were encountered:
hkulekci
changed the title
Multiple Metadata Feature Implementation
Multiple Metadata Source Feature Implementation
Jun 14, 2016
hkulekci
changed the title
Multiple Metadata Source Feature Implementation
Multiple Metadata Source FeatureUsage Implementation
Jun 14, 2016
edigu
changed the title
Multiple Metadata Source FeatureUsage Implementation
DriverChain implementation example (Multiple metadata source)
Jun 14, 2016
edigu
changed the title
DriverChain implementation example (Multiple metadata source)
DriverChain usage example (Multiple metadata source)
Jun 14, 2016
from the documentation :
Multiple Metadata Sources
When using different components with Doctrine 2, you may end up with them using two different metadata drivers, for example, XML and YAML. You can use the DriverChain Metadata implementations to aggregate these drivers based on namespaces:
Based on the namespace of the entity the loading of entities is delegated to the appropriate driver. The chain semantics come from the fact that the driver loops through all namespaces and matches the entity class name against the namespace using a
strpos() === 0
call. This means you need to order the drivers correctly if sub-namespaces use different metadata driver implementations.The text was updated successfully, but these errors were encountered: