> Hello,

> Need a little bit of help here, because I seem to be going round in
> circles.  Before I start, I have done a fair amount of research on this
> issue and have tried the solutions that have been suggested in the
> JMSSerializerBundle docs as well as other configuration tweaks.

> Basically, I'm using FOSRestBundle to serve up an API and I chose a simple
> use case to prove concept before I embark on the actual business logic.  
> I'm trying to spit out JSON representing a filtered version of
> \FOS\UserBundle\Propel\User but the output always contains a whole bunch of
> extra fields that should have been omitted via XML configuration.

> As far as I can tell, I've followed the instructions to the letter so I'm
> a bit stumped.  See code below ("foo" and "bar" swapped in for actual
> sensitive information)

> # ./serializer/fos/Propel.User.xml
> <serializer>  
>     <class name="FOS\UserBundle\Propel\User" exclusion-policy="all">  
>         <property name="id" type="integer" expose="true"
> access-type="public_method"></property>  
>         <property name="username" type="string" expose="true"
> access-type="public_method"></property>  
>         <property name="usernameCanonical" type="string" expose="true"
> access-type="public_method"></property>  
>         <property name="email" type="string" expose="true"
> access-type="public_method"></property>  
>         <property name="emailCanonical" type="string" expose="true"
> access-type="public_method"></property>  
>     </class>  
> </serializer>

> # ./app/config/config.yml
> ...

> jms_serializer:
>     metadata:
>         directories:
>             FOSUB:
>                 namespace_prefix: FOS\UserBundle
>                 path: "%kernel.root_dir%/serializer/fos"

> # ./src/Foo/BarBundle/Controller/UserRestController.php
> <?php

> namespace Foo\BarBundle\Controller;

> use Symfony\Bundle\FrameworkBundle\Controller\Controller;

> class UserRestController extends Controller
> {
>     public function getUserAction($userId)
>     {
>         $user = $this->get('security.context')->getToken()->getUser();

>         if ($user) {
>             $view = \FOS\RestBundle\View\View::create($user, 200);
>         } else {
>             $view = \FOS\RestBundle\View\View::create(null, 404);
>         }

>         return $this->get('fos_rest.view_handler')->handle($view);
>     }
> }

> And here's the output I'm getting - seems that all the state properties of
> the Propel object are being included.

> {"_new":false,"_deleted":false,"modified_columns":[],"virtual_columns":[]," start_copy":false,"id":1,"username":"foo","username_canonical":"foo","email ":"f...@bar.com","email_canonical":"f...@bar.com","enabled":true,"salt":"salt","password":"password","last_login":" 2012-10-08 09:49:38","locked":false,"expired":false,"credentials_expired":false,"alrea dy_in_save":false,"already_in_validation":false,"validation_failures":[]}

> I looked in the dev cache, and there are a few files with serialized
> contents corresponding to my configuration.

> # ./app/cache/dev/jms_serializer/BaseObject.cache.php
> #
> ./app/cache/dev/jms_serializer/FOS-UserBundle-Propel-om-BaseUser.cache.php
> # ./app/cache/dev/jms_serializer/FOS-UserBundle-Propel-User.cache.php

> Has anyone had any experience using this serializer bundle with Propel
> objects before? If so, what did you do to get it working?

> Thanks in advance,
> Nick.

> Hello,

> Well, I've made progress.  I stuck the serializer configuration into YML
> (pointing at the Propel base class), stuck the file under my main bundle's
> config directory (created a serializer directory) and was able to return a
> filtered, serialized version of the User object.

> However, I am getting additional fields coming through despite the
> configuration explicitly set to "expose: false".

> # ./app/config/config.yml
> jms_serializer:
>     metadata:
>         auto_detection: true
>         directories:
>             fos:
>                 namespace_prefix: "FOS\\UserBundle"
>                 path: "@FooBarBundle/Resources/config/serializer"

> # ./src/Foo/BarBundle/Resources/config/serializer/Propel.om.BaseUser.yml
> FOS\UserBundle\Propel\om\BaseUser:
>     exclusion_policy: ALL
>     access_type: public_method
>     properties:
>         id:
>             expose: true
>         username:
>             expose: true
>         email:
>             expose: true
>         _new:
>             expose: false
>         _deleted:
>             expose: false
>         modified_columns:
>             expose: false
>         virtual_columns:
>             expose: false

> An example of the JSON being returned:

> {"_new":false,"_deleted":false,"modified_columns":[],"virtual_columns":[]," id":1,"username":"foo","email":"f...@bar.com"}

> I only want the values from the User class, not the meta properties from
> Propel's base classes.  Any idea what I'm doing wrong?

> Cheers,
> Nick.

> On Monday, October 8, 2012 9:59:07 AM UTC+1, Nick Winfield wrote:

>> Hello,

>> Need a little bit of help here, because I seem to be going round in
>> circles.  Before I start, I have done a fair amount of research on this
>> issue and have tried the solutions that have been suggested in the
>> JMSSerializerBundle docs as well as other configuration tweaks.

>> Basically, I'm using FOSRestBundle to serve up an API and I chose a
>> simple use case to prove concept before I embark on the actual business
>> logic.  I'm trying to spit out JSON representing a filtered version of
>> \FOS\UserBundle\Propel\User but the output always contains a whole bunch of
>> extra fields that should have been omitted via XML configuration.

>> As far as I can tell, I've followed the instructions to the letter so I'm
>> a bit stumped.  See code below ("foo" and "bar" swapped in for actual
>> sensitive information)

>> # ./serializer/fos/Propel.User.xml
>> <serializer>  
>>     <class name="FOS\UserBundle\Propel\User" exclusion-policy="all">  
>>         <property name="id" type="integer" expose="true"
>> access-type="public_method"></property>  
>>         <property name="username" type="string" expose="true"
>> access-type="public_method"></property>  
>>         <property name="usernameCanonical" type="string" expose="true"
>> access-type="public_method"></property>  
>>         <property name="email" type="string" expose="true"
>> access-type="public_method"></property>  
>>         <property name="emailCanonical" type="string" expose="true"
>> access-type="public_method"></property>  
>>     </class>  
>> </serializer>

>> # ./app/config/config.yml
>> ...

>> jms_serializer:
>>     metadata:
>>         directories:
>>             FOSUB:
>>                 namespace_prefix: FOS\UserBundle
>>                 path: "%kernel.root_dir%/serializer/fos"

>> # ./src/Foo/BarBundle/Controller/UserRestController.php
>> <?php

>> namespace Foo\BarBundle\Controller;

>> use Symfony\Bundle\FrameworkBundle\Controller\Controller;

>> class UserRestController extends Controller
>> {
>>     public function getUserAction($userId)
>>     {
>>         $user = $this->get('security.context')->getToken()->getUser();

>>         if ($user) {
>>             $view = \FOS\RestBundle\View\View::create($user, 200);
>>         } else {
>>             $view = \FOS\RestBundle\View\View::create(null, 404);
>>         }

>>         return $this->get('fos_rest.view_handler')->handle($view);
>>     }
>> }

>> And here's the output I'm getting - seems that all the state properties
>> of the Propel object are being included.

>> {"_new":false,"_deleted":false,"modified_columns":[],"virtual_columns":[]," start_copy":false,"id":1,"username":"foo","username_canonical":"foo","email ":"f...@bar.com","email_canonical":"f...@bar.com","enabled":true,"salt":"salt","password":"password","last_login":" 2012-10-08 09:49:38","locked":false,"expired":false,"credentials_expired":false,"alrea dy_in_save":false,"already_in_validation":false,"validation_failures":[]}

>> I looked in the dev cache, and there are a few files with serialized
>> contents corresponding to my configuration.

>> # ./app/cache/dev/jms_serializer/BaseObject.cache.php
>> #
>> ./app/cache/dev/jms_serializer/FOS-UserBundle-Propel-om-BaseUser.cache.php
>> # ./app/cache/dev/jms_serializer/FOS-UserBundle-Propel-User.cache.php

>> Has anyone had any experience using this serializer bundle with Propel
>> objects before? If so, what did you do to get it working?

>> Thanks in advance,
>> Nick.

> I'm working on learning how to use JMSSerializerBundle + FOSUserBundle
> to build a REST api with Symfony 2. I'll be referencing this thread if
> I run into similar problems. You can rest assure that at least one
> person is reading all of this.

> On Mon, Oct 8, 2012 at 11:23 AM, Nick Winfield <pio...@superhaggis.com<javascript:>>
> wrote:
> > Hello again,

> > Even though it feels like I'm talking to myself, I thought I'd share my
> > solution. :P

> > In order to get things working, however, I had to patch in the following
> PR
> > for the metadata package.

> https://github.com/schmittjoh/metadata/commit/64ce1d44fd91c27c1426f21...

> > Basically, I had to exclude all properties accessible via public methods
> > from the BaseObject class in Propel.  The reason I had to patch metadata
> was
> > because the BaseObject class, where the unwanted properties reside, does
> not
> > have a namespace.

> > # ./app/config/config.yml
> > jms_serializer:
> >     metadata:
> >         auto_detection: true
> >         directories:
> >             propel:
> >                 namespace_prefix: ""
> >                 path: "@FooBarBundle/Resources/config/serializer"

> >             fos:
> >                 namespace_prefix: "FOS\\UserBundle"
> >                 path: "@FooBarBundle/Resources/config/serializer"

> > # ./src/Foo/BarBundle/Resources/config/serializer/BaseObject.yml
> > BaseObject:
> >     exclusion_policy: ALL

> > I cleared my dev cache and was able to view a trimmed down serialized
> > representation of the User object.

> > {"id":1,"username":"foo","email":"f...@bar.com <javascript:>"}

> > I hope my solution is of help to someone!

> > Cheers,
> > Nick.

> > On Monday, October 8, 2012 2:49:37 PM UTC+1, Nick Winfield wrote:

> >> Hello,

> >> Well, I've made progress.  I stuck the serializer configuration into
> YML
> >> (pointing at the Propel base class), stuck the file under my main
> bundle's
> >> config directory (created a serializer directory) and was able to
> return a
> >> filtered, serialized version of the User object.

> >> However, I am getting additional fields coming through despite the
> >> configuration explicitly set to "expose: false".

> >> # ./app/config/config.yml
> >> jms_serializer:
> >>     metadata:
> >>         auto_detection: true
> >>         directories:
> >>             fos:
> >>                 namespace_prefix: "FOS\\UserBundle"
> >>                 path: "@FooBarBundle/Resources/config/serializer"

> >> #
> ./src/Foo/BarBundle/Resources/config/serializer/Propel.om.BaseUser.yml
> >> FOS\UserBundle\Propel\om\BaseUser:
> >>     exclusion_policy: ALL
> >>     access_type: public_method
> >>     properties:
> >>         id:
> >>             expose: true
> >>         username:
> >>             expose: true
> >>         email:
> >>             expose: true
> >>         _new:
> >>             expose: false
> >>         _deleted:
> >>             expose: false
> >>         modified_columns:
> >>             expose: false
> >>         virtual_columns:
> >>             expose: false

> >> An example of the JSON being returned:

> {"_new":false,"_deleted":false,"modified_columns":[],"virtual_columns":[]," id":1,"username":"foo","email":"
> f...@bar.com <javascript:>"}

> >> I only want the values from the User class, not the meta properties
> from
> >> Propel's base classes.  Any idea what I'm doing wrong?

> >> Cheers,
> >> Nick.

> >> On Monday, October 8, 2012 9:59:07 AM UTC+1, Nick Winfield wrote:

> >>> Hello,

> >>> Need a little bit of help here, because I seem to be going round in
> >>> circles.  Before I start, I have done a fair amount of research on
> this
> >>> issue and have tried the solutions that have been suggested in the
> >>> JMSSerializerBundle docs as well as other configuration tweaks.

> >>> Basically, I'm using FOSRestBundle to serve up an API and I chose a
> >>> simple use case to prove concept before I embark on the actual
> business
> >>> logic.  I'm trying to spit out JSON representing a filtered version of
> >>> \FOS\UserBundle\Propel\User but the output always contains a whole
> bunch of
> >>> extra fields that should have been omitted via XML configuration.

> >>> As far as I can tell, I've followed the instructions to the letter so
> I'm
> >>> a bit stumped.  See code below ("foo" and "bar" swapped in for actual
> >>> sensitive information)

> >>> # ./serializer/fos/Propel.User.xml
> >>> <serializer>
> >>>     <class name="FOS\UserBundle\Propel\User" exclusion-policy="all">
> >>>         <property name="id" type="integer" expose="true"
> >>> access-type="public_method"></property>
> >>>         <property name="username" type="string" expose="true"
> >>> access-type="public_method"></property>
> >>>         <property name="usernameCanonical" type="string" expose="true"
> >>> access-type="public_method"></property>
> >>>         <property name="email" type="string" expose="true"
> >>> access-type="public_method"></property>
> >>>         <property name="emailCanonical" type="string" expose="true"
> >>> access-type="public_method"></property>
> >>>     </class>
> >>> </serializer>

> >>> # ./app/config/config.yml
> >>> ...

> >>> jms_serializer:
> >>>     metadata:
> >>>         directories:
> >>>             FOSUB:
> >>>                 namespace_prefix: FOS\UserBundle
> >>>                 path: "%kernel.root_dir%/serializer/fos"

> >>> # ./src/Foo/BarBundle/Controller/UserRestController.php
> >>> <?php

> >>> namespace Foo\BarBundle\Controller;

> >>> use Symfony\Bundle\FrameworkBundle\Controller\Controller;

> >>> class UserRestController extends Controller
> >>> {
> >>>     public function getUserAction($userId)
> >>>     {
> >>>         $user = $this->get('security.context')->getToken()->getUser();

> >>>         if ($user) {
> >>>             $view = \FOS\RestBundle\View\View::create($user, 200);
> >>>         } else {
> >>>             $view = \FOS\RestBundle\View\View::create(null, 404);
> >>>         }

> >>>         return $this->get('fos_rest.view_handler')->handle($view);
> >>>     }
> >>> }

> >>> And here's the output I'm getting - seems that all the state
> properties
> >>> of the Propel object are being included.

> {"_new":false,"_deleted":false,"modified_columns":[],"virtual_columns":[]," start_copy":false,"id":1,"username":"foo","username_canonical":"foo","email ":"
> f...@bar.com <javascript:>","email_canonical":"f...@bar.com <javascript:>","enabled":true,"salt":"salt","password":"password","last_log in":"2012-10-08

> 09:49:38","locked":false,"expired":false,"credentials_expired":false,"alrea dy_in_save":false,"already_in_validation":false,"validation_failures":[]}

> >>> I looked in the dev cache, and there are a few files with serialized
> >>> contents corresponding to my configuration.

> >>> # ./app/cache/dev/jms_serializer/BaseObject.cache.php
> >>> #

> ./app/cache/dev/jms_serializer/FOS-UserBundle-Propel-om-BaseUser.cache.php
> >>> # ./app/cache/dev/jms_serializer/FOS-UserBundle-Propel-User.cache.php

> >>> Has anyone had any experience using this serializer bundle with Propel
> >>> objects before? If so, what did you do to get it working?

> >>> Thanks in advance,
> >>> Nick.

> > --
> > If you want to report a vulnerability issue on symfony, please send it
> to
> > security at symfony-project.com

> > You received this message because you are subscribed to the Google
> > Groups "Symfony2" group.
> > To post to this group, send email to symf...@googlegroups.com<javascript:>
> > To unsubscribe from this group, send email to
> > symfony2+u...@googlegroups.com <javascript:>
> > For more options, visit this group at
> > http://groups.google.com/group/symfony2?hl=en

> --
> ----------------------------------------------
> "May the Source be with you."

> Hello,

> Need a little bit of help here, because I seem to be going round in
> circles.  Before I start, I have done a fair amount of research on this
> issue and have tried the solutions that have been suggested in the
> JMSSerializerBundle docs as well as other configuration tweaks.

> Basically, I'm using FOSRestBundle to serve up an API and I chose a simple
> use case to prove concept before I embark on the actual business logic.  
> I'm trying to spit out JSON representing a filtered version of
> \FOS\UserBundle\Propel\User but the output always contains a whole bunch of
> extra fields that should have been omitted via XML configuration.

> As far as I can tell, I've followed the instructions to the letter so I'm
> a bit stumped.  See code below ("foo" and "bar" swapped in for actual
> sensitive information)

> # ./serializer/fos/Propel.User.xml
> <serializer>  
>     <class name="FOS\UserBundle\Propel\User" exclusion-policy="all">  
>         <property name="id" type="integer" expose="true"
> access-type="public_method"></property>  
>         <property name="username" type="string" expose="true"
> access-type="public_method"></property>  
>         <property name="usernameCanonical" type="string" expose="true"
> access-type="public_method"></property>  
>         <property name="email" type="string" expose="true"
> access-type="public_method"></property>  
>         <property name="emailCanonical" type="string" expose="true"
> access-type="public_method"></property>  
>     </class>  
> </serializer>

> # ./app/config/config.yml
> ...

> jms_serializer:
>     metadata:
>         directories:
>             FOSUB:
>                 namespace_prefix: FOS\UserBundle
>                 path: "%kernel.root_dir%/serializer/fos"

> # ./src/Foo/BarBundle/Controller/UserRestController.php
> <?php

> namespace Foo\BarBundle\Controller;

> use Symfony\Bundle\FrameworkBundle\Controller\Controller;

> class UserRestController extends Controller
> {
>     public function getUserAction($userId)
>     {
>         $user = $this->get('security.context')->getToken()->getUser();

>         if ($user) {
>             $view = \FOS\RestBundle\View\View::create($user, 200);
>         } else {
>             $view = \FOS\RestBundle\View\View::create(null, 404);
>         }

>         return $this->get('fos_rest.view_handler')->handle($view);
>     }
> }

> And here's the output I'm getting - seems that all the state properties of
> the Propel object are being included.

> {"_new":false,"_deleted":false,"modified_columns":[],"virtual_columns":[]," start_copy":false,"id":1,"username":"foo","username_canonical":"foo","email ":"f...@bar.com <javascript:>","email_canonical":"f...@bar.com <javascript:>","enabled":true,"salt":"salt","password":"password","last_log in":"2012-10-08 09:49:38","locked":false,"expired":false,"credentials_expired":false,"alrea dy_in_save":false,"already_in_validation":false,"validation_failures":[]}

> I looked in the dev cache, and there are a few files with serialized
> contents corresponding to my configuration.

> # ./app/cache/dev/jms_serializer/BaseObject.cache.php
> #
> ./app/cache/dev/jms_serializer/FOS-UserBundle-Propel-om-BaseUser.cache.php
> # ./app/cache/dev/jms_serializer/FOS-UserBundle-Propel-User.cache.php

> Has anyone had any experience using this serializer bundle with Propel
> objects before? If so, what did you do to get it working?

> Thanks in advance,
> Nick.

> Hello again,

> Even though it feels like I'm talking to myself, I thought I'd share my
> solution. :P

> In order to get things working, however, I had to patch in the following
> PR for the metadata package.

> https://github.com/schmittjoh/metadata/commit/64ce1d44fd91c27c1426f21...

> Basically, I had to exclude all properties accessible via public methods
> from the BaseObject class in Propel.  The reason I had to patch metadata
> was because the BaseObject class, where the unwanted properties reside,
> does not have a namespace.

> # ./app/config/config.yml
> jms_serializer:
>     metadata:
>         auto_detection: true
>         directories:
>             propel:
>                 namespace_prefix: ""
>                 path: "@FooBarBundle/Resources/config/serializer"
>             fos:
>                 namespace_prefix: "FOS\\UserBundle"
>                 path: "@FooBarBundle/Resources/config/serializer"

> # ./src/Foo/BarBundle/Resources/config/serializer/BaseObject.yml
> BaseObject:
>     exclusion_policy: ALL

> I cleared my dev cache and was able to view a trimmed down serialized
> representation of the User object.

> {"id":1,"username":"foo","email":"f...@bar.com <javascript:>"}

> I hope my solution is of help to someone!

> Cheers,
> Nick.

> On Monday, October 8, 2012 2:49:37 PM UTC+1, Nick Winfield wrote:

>> Hello,

>> Well, I've made progress.  I stuck the serializer configuration into YML
>> (pointing at the Propel base class), stuck the file under my main bundle's
>> config directory (created a serializer directory) and was able to return a
>> filtered, serialized version of the User object.

>> However, I am getting additional fields coming through despite the
>> configuration explicitly set to "expose: false".

>> # ./app/config/config.yml
>> jms_serializer:
>>     metadata:
>>         auto_detection: true
>>         directories:
>>             fos:
>>                 namespace_prefix: "FOS\\UserBundle"
>>                 path: "@FooBarBundle/Resources/config/serializer"

>> # ./src/Foo/BarBundle/Resources/config/serializer/Propel.om.BaseUser.yml
>> FOS\UserBundle\Propel\om\BaseUser:
>>     exclusion_policy: ALL
>>     access_type: public_method
>>     properties:
>>         id:
>>             expose: true
>>         username:
>>             expose: true
>>         email:
>>             expose: true
>>         _new:
>>             expose: false
>>         _deleted:
>>             expose: false
>>         modified_columns:
>>             expose: false
>>         virtual_columns:
>>             expose: false

>> An example of the JSON being returned:

>> {"_new":false,"_deleted":false,"modified_columns":[],"virtual_columns":[]," id":1,"username":"foo","email":"f...@bar.com <javascript:>"}

>> I only want the values from the User class, not the meta properties from
>> Propel's base classes.  Any idea what I'm doing wrong?

>> Cheers,
>> Nick.

>> On Monday, October 8, 2012 9:59:07 AM UTC+1, Nick Winfield wrote:

>>> Hello,

>>> Need a little bit of help here, because I seem to be going round in
>>> circles.  Before I start, I have done a fair amount of research on this
>>> issue and have tried the solutions that have been suggested in the
>>> JMSSerializerBundle docs as well as other configuration tweaks.

>>> Basically, I'm using FOSRestBundle to serve up an API and I chose a
>>> simple use case to prove concept before I embark on the actual business
>>> logic.  I'm trying to spit out JSON representing a filtered version of
>>> \FOS\UserBundle\Propel\User but the output always contains a whole bunch of
>>> extra fields that should have been omitted via XML configuration.

>>> As far as I can tell, I've followed the instructions to the letter so
>>> I'm a bit stumped.  See code below ("foo" and "bar" swapped in for actual
>>> sensitive information)

>>> # ./serializer/fos/Propel.User.xml
>>> <serializer>  
>>>     <class name="FOS\UserBundle\Propel\User" exclusion-policy="all">  
>>>         <property name="id" type="integer" expose="true"
>>> access-type="public_method"></property>  
>>>         <property name="username" type="string" expose="true"
>>> access-type="public_method"></property>  
>>>         <property name="usernameCanonical" type="string" expose="true"
>>> access-type="public_method"></property>  
>>>         <property name="email" type="string" expose="true"
>>> access-type="public_method"></property>  
>>>         <property name="emailCanonical" type="string" expose="true"
>>> access-type="public_method"></property>  
>>>     </class>  
>>> </serializer>

>>> # ./app/config/config.yml
>>> ...

>>> jms_serializer:
>>>     metadata:
>>>         directories:
>>>             FOSUB:
>>>                 namespace_prefix: FOS\UserBundle
>>>                 path: "%kernel.root_dir%/serializer/fos"

>>> # ./src/Foo/BarBundle/Controller/UserRestController.php
>>> <?php

>>> namespace Foo\BarBundle\Controller;

>>> use Symfony\Bundle\FrameworkBundle\Controller\Controller;

>>> class UserRestController extends Controller
>>> {
>>>     public function getUserAction($userId)
>>>     {
>>>         $user = $this->get('security.context')->getToken()->getUser();

>>>         if ($user) {
>>>             $view = \FOS\RestBundle\View\View::create($user, 200);
>>>         } else {
>>>             $view = \FOS\RestBundle\View\View::create(null, 404);
>>>         }

>>>         return $this->get('fos_rest.view_handler')->handle($view);
>>>     }
>>> }

>>> And here's the output I'm getting - seems that all the state properties
>>> of the Propel object are being included.

>>> {"_new":false,"_deleted":false,"modified_columns":[],"virtual_columns":[]," start_copy":false,"id":1,"username":"foo","username_canonical":"foo","email ":"f...@bar.com <javascript:>","email_canonical":"f...@bar.com <javascript:>","enabled":true,"salt":"salt","password":"password","last_log in":"2012-10-08 09:49:38","locked":false,"expired":false,"credentials_expired":false,"alrea dy_in_save":false,"already_in_validation":false,"validation_failures":[]}

>>> I looked in the dev cache, and there are a few files with serialized
>>> contents corresponding to my configuration.

>>> # ./app/cache/dev/jms_serializer/BaseObject.cache.php
>>> #
>>> ./app/cache/dev/jms_serializer/FOS-UserBundle-Propel-om-BaseUser.cache.php
>>> # ./app/cache/dev/jms_serializer/FOS-UserBundle-Propel-User.cache.php

>>> Has anyone had any experience using this serializer bundle with Propel
>>> objects before? If so, what did you do to get it working?

>>> Thanks in advance,
>>> Nick.