jmsserializerbundle

I am attempting to use JMSSerializer as a stand alone library to map JSON responses from an API to my model classes and am running into some issues. Executing the following code results in an exception: <?php require dirname(__DIR__) . '/vendor/autoload.php'; use JMS\Serializer\Annotation AS JMS; class Trii { /** * User ID for this session * @JMS\SerializedName("userID") * @JMS\Annotation(getter="getUserId") * @JMS\Type("string") * @var string */ private $userId; public function getUserId() { return $this->userId; } public function setUserId($userId) { $this->userId = $userId; } } $serializer

I'm trying to update symfony2/doctrine entities using JMSSerializer with an @ExclusionPolicy:None @Groups Inclusion Policy. * @Serializer\ExclusionPolicy("none") */ class Foo { /** * @Serializer\Groups({"flag","edit"}) */ protected $id; /** * @Serializer\Groups({"edit"}) */ protected $name; /** * @Serializer\Groups({"flag"}) */ protected $flag; /** * @Serializer\Exclude() */ protected $createdBy; } reference: http://jmsyst.com/libs/serializer/master/reference/annotations the result for the following record: Foo (id:1, name:'bar', flagged:false ,created_by:123) is serialized using Group

Im using Doctrine 2 ORM in my Zend project and need to serialize my Entities to JSON in several cases. ATM i use the Querybuilder and join all tables i need. But my serializer causes doctrine to lazy load every associated Entity which results in pretty huge data amounts and provokes recursion. Now im looking for a way to totally disable Doctrines lazy loading behavior. My way to select data would be the following: $qb= $this->_em->createQueryBuilder() ->from("\Project\Entity\Personappointment", 'pa') ->select('pa', 't', 'c', 'a', 'aps', 'apt', 'p') ->leftjoin('pa.table', 't') ->leftjoin('pa

I have two entities I wish to serialize with the JMSSerializerBundle. The Music Entity has a mapping-file with exclusion_policy: NONE . The Music entity has a field of the entity User from FOSUserBundle . The User entity has a mapping-file with exclusion_policy: ALL with a few fields set to expose: true , so they will be serialized. The problem is, the User field gets fully serialized. It does not matter if I change the mapping-file of the User entity. This is how it looks: #My/Bundle/Resources/config/serializer/Entity.Music.yml xxx\xxx\Entity\Music: exclusion_policy: NONE #My/Bundle/Resources