But some the ValueObject classes contain a reference to an entity. Keep in mind I mean ValueObject in the context of domain driven design, not a DTO / data transfer object.
On Tue, 2009-11-10 at 22:12 -0500, James Carman wrote: > ValueObjects (if you're following the design pattern) should be serializable. > > On Tue, Nov 10, 2009 at 10:03 PM, Sam Barrow <s...@sambarrow.com> wrote: > > > > One more question about serializing objects. > > I have a page in the application that I'm working on that calls an > > application service which returns a collection of objects of a type I'll > > call ValueObject (not serializable). ValueObject has many subclasses > > (which are of no concern to my wicket ui, which only deals with the > > ValueObject interface). > > > > So i have a page which calls the service and now has a collection of > > ValueObjects. What is the best way to pass this object to another page? > > Keep in mind it is not serializable and has no identity i can look it up > > by > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
