adaptor pattern with MVC

I went this route recently, but soon refactored into a much simpler design. The problem I found with this approach of wrapping domain objects is that you soon end up with lots of adaptations of the same object, resulting in a lot of duplicate code throughout your adaptors. You could refactor this common code out into a helper but that just adds to a growing list of classes.

An alternative which worked well for me was to reuse the domain objects themselves in the view, and have a view helper handle any awkwardness of dealing with them, (e.g. data convertions) .

Of course I dont know enough about your particular design to suggest this approach, but thought it might interest you as an alternative :o)

rhydthoma at 2007-7-16 1:57:52 >