also support a path/id string as a valid value for $contentDocument in the ContentController

[lsmith77]

this way it will become possible to use the ContentController in combination with ESI/SSI subrequests. if a string is provided, then we do an automatic look up in the object manager. however this would require injecting an object manager. to make things work with the ORM, we would then also need to optionally set a class name, though maybe this should then also be a dynamic parameter?

[dbu]

i think this is difficult. the routing relies on the content being an object for looking up the right controller, and the template. doing this we either re-implement the route enhancer process in the controller or would need a way to re-trigger that process from the controller.

what is the situation where the routing can not determine the object and put that into contentDocument? maybe we could have a request listener that converts this to an object, if there is a valid use case.

[dbu]

maybe doctrine/DoctrinePHPCRBundle#172 is the thing we really want to do

[lsmith77]

yeah