make the ManagerRegistry service configurable

[lsmith77]

fix for #73

[stof]

-1 for exposing it in the semantic config. It is a complex edge case, and the custom class might require more changes than just the class name (more dependencies to determine the manager for instance).

IMO, people wanting this should either overwrite the parameter themselves directly, or use a compiler pass to edit the definition if they need more stuff (or use the new decorates stuff in Symfony 2.5+). Cluttering the smeantic config with this is not worth it IMO

[dantleech]

What if instead of the specifying the class name we specify the service ID?

We can then use an alias to define doctrine_phpcr and assign it to the configured service ID.

[lsmith77]

in some places we allow configuring class names and in others services. both works for me i guess. but what else would you want to inject given that the registry has access to the container?

[dantleech]

don't know - but you have the option of not injecting the container I guess.

[lsmith77]

@stof well we were saying this is the solution for be able to do stuff like switching elegantly between a staging and production workspace. as such it is not such an edge case for quite a few CMS. but ok lets make the service configurable rather than the class.

[lsmith77]

done

[dbu]

why do you expand these? its not adding anything. i can live with it, just don't see why.

[lsmith77]

right. this was from a previous version of the patch. will remove

[dbu]

+1 on the way its done now, allowing to specify the service id for full customization. user can still use the di container parameter if he just needs a different class.

[dbu]

thanks. created symfony-cmf/symfony-cmf-docs#558 so we don't forget about the doc.