|
Hi, I have developed a couple of very simple ARP projects that deal with a list of things that do not change, e.g. the PizzaService idea was developed so that the Pizza model became an Image and the OrderVO became a ProductVO that has a number of Images associated with it. I now wish to extend this idea to develop a gallery application with facilities to edit images, galleries, etc. Because I want to load up a list of Image Models, I am assuming that I would have some kind of ImageListVO that contains Image Models ~ OrderVO. But, because I want to change the contents of these Image Models and save them back to the server, does this mean that they should essentially become VO's? The question I am trying to get an answer to is; "when does a Model become a VO?". The next question is "How do I deal with Lists of VO's?" - I am guessing I need some sort of container for these, but if my container is a Gallery it has editable properties too. I have looked into a couple of patterns such as Value List Handler on the J2EE site, but the concept of a Transfer Object, as opposed to a Value Object , has confused. Any help, better links and direction would be greatly appreciated. Thanks in advance. Glen Pike www.glenpike.co.uk |
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
