On 2010-07-30 16.49, Marc Grue wrote:
I have a problem serializing a ValueComposite when I pass it from one page
to another in Wicket. Wicket is checking if the properties of the
ValueComposite are serializable, and somewhere in the process (that's where
I get lost) we have a runtime.value.ValueInstance which is not a
Serializable. Since a ValueComposite is Serializable, shouldn't the
ValueInstances be so too? Shouldn't Wicket be able to serialize my
UserEntityDTO, or am I missing something basic?
I think Niclas was working around this issue in
http://old.nabble.com/ValueComposites-are-not-%27type-proxied%27-like-other-Composites.-td22072609.html#a22072609
Hm... I think the Composite extends Serializable is a left-over. They
shouldn't be. Am I missing something Niclas? The problem is that the
deserialization process needs a lot of context (i.e. you need your own
ObjectInputStream that has access to Composite factories and whatnot),
and I don't think we ever figured out how to do that properly.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
