Problem when using Doctrine Embedded/Embeddable

[teohhanhui]

http://doctrine-orm.readthedocs.org/en/latest/tutorials/embeddables.html

Currently it dies at Dunglas\ApiBundle\JsonLd\Serializer\ItemNormalizer::getIriFromItem. I think the embedded object should be serialized as a plain object?

[dunglas]

I never tried to work with embedded objects. But yes it sounds good to be serialized as a plain object.

[teohhanhui]

From my reading of the code it seems like it will even cause problems with other objects that are not Doctrine entities and/or not a "resource" at all (due to Dunglas\ApiBundle\JsonLd\Serializer\ItemNormalizer::normalize and Dunglas\ApiBundle\Api\ResourceResolverTrait::guessResource), or am I missing something?

[dunglas]

Yes. For now any object exposed must be associated to a Resource (in fact should be better called ResourceType) class.
The only currently supported way to "embed" raw data structures is associative array.

[teohhanhui]

It'd be nice if I can use Symfony\Component\Serializer\Normalizer\ObjectNormalizer to convert the (offending) object into associative array before being passed to Dunglas\ApiBundle\JsonLd\Serializer\ItemNormalizer

Is that possible?

[teohhanhui]

But I think the more ideal solution would still be to have it as a Resource without identifier / @id (is that valid?)

[dunglas]

I think it's a better idea to use ObjectNormalizer. A Resource represent a REST resource (exposed trough an URL), not an internal object (I'll write some doc about the terminology when I'll be less busy).

[teohhanhui]

The primary use case would be for StructuredValue and its subtypes. How would I go about embedding such an object while still having it properly identified as such (if at all possible)...

[dunglas]

In that case you don't need Doctrine Embedded/Embeddable IMO. A typical relation between 2 entities should do the work.

[theofidry]

Duplicate of #166: how to handle entities (embedded or not) which are internal object and not a REST resource.