QueryResultProxy not Serializable [DATAGRAPH-311]

[spring-projects-issues]

Michael Andrews opened DATAGRAPH-311 and commented

I'm trying to send a mapped Neo4j query result object (a @MapResult Interface, proxied by QueryResultProxy) over to another JVM using Spring Remoting. Seems the QueryResultProxy object graph is not Serializable. I'm not really sure how the QueryResultProxy works - but I think Spring AOP proxies are serializable. Should the QueryResultProxy be Serializable?

---

Affects: 2.1

Referenced from: commits d1a2892, bf60ad3, 764611c, 8bb6313, bc5a271

[spring-projects-issues]

Michael Hunger commented

Andrew,

QueryResultProxy is only a Java Dynamic Proxy b/c we wanted to make it work with non AOP setups too, but we want to add support for projecting into real classes too, so you can easily transport them over the wire

[spring-projects-issues]

Michael Andrews commented

Michael - Thanks for the reply. That would be great. The @MappedResult is a powerful feature and it would be nice to have the implementation serializable. Neo4j is an exciting technology. Glad there is such rich support for it in Spring Data

[spring-projects-issues]

Michael Andrews commented

Is there a roadmap for this? any update, or fix release set? thanks. M

[spring-projects-issues]

Michael Hunger commented

Michael,

not yet, don't know if we can make it in the next release (2.2.0) I try to but cannot promise. Have to think about if it should align with @NodeEntity mappings with persistence constructor support or a separate feature (just plain DTOs mapped to cypher query results)

[spring-projects-issues]

Nicki Watt commented

Done via PR #124