The ORM uses proxy classes internally. Thus, while working with the proxies (when you load stuff from DB you usually receive a proxy from the Object Hydrator), you don't have access to private vars defined in your entities. That's why serialization of a proxy fails (and you should not serialize proxies! detach them from the entity manager first to get a clean POPO!)
Marco Pivetta @Ocramius <http://twitter.com/Ocramius> http://marco-pivetta.com On 11 May 2011 01:10, Christophe COEVOET <s...@notk.org> wrote: > Le 10/05/2011 13:25, AndyPI a écrit : > > Don't know if it helps, but changing my variables from 'private' to >> 'protected' in Symfony2 entities removed this problem for me. >> >> The Symfony2 docs use protected in their examples, but the console >> generates variables as private. Something to look at? >> > The Doctrine doc advices to use the \Serializable interface: > http://www.doctrine-project.org/docs/orm/2.0/en/reference/architecture.html > > -- > Christophe | Stof > > -- > 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 "symfony users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- 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 "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
