Then just keep the criteria to get those items in your components?
samb0057 wrote: > > The value objects are not simple attributes of an entity. Let me explain > what they do (a little simplified but the fundamentals are there). > > We have a research module that performs pricing research. > > ResearchItem > CellPhoneResearchItem > IPodResearchItem > LaptopResearchItem > Etc > > Since the identity of these research items is defined solely by their > attributes they are implemented as value objects. I know this is different > from your everyday value object (eg Address) Does this sound like maybe a > problem that should be addressed in the domain model? > Value objects were chosen since it makes it much easier in many other > areas to just create a new research item, rather than call repositories to > load old ones (impossible in some places). No point in loading something > you know all the attributes of. > > The only way to get them reliably is to call > ResearchItemGenerationService.generateResearchItems() > -- View this message in context: http://old.nabble.com/another-serialization-question-tp26295325p26297467.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
