Maybe 'cause tiers don't mean anything now... Your GUI is splitted in tiers itself (server-side, JavaScript, Flex, you-name-it), as well as the back end...
Tiers are an old principle that was relevant during the heavy client/server stuff we've been coding in the nineties, but today's webapps made it quite non relevant. They are not 3-tier, they are n-tier, btw. What matters in the end is "can you ship it", "how much", and "how much for the maintenance". In that respect, binding to domain models and using persistent entities in the web tier is clearly arguable. That's basically what ALL domain driven frameworks do (Grails, RoR, you name it), and, well, it just works. Of course your "gray-haired computer science teacher who never coded any real life app" would not agree. But do you really care ? :P Cheers Remi 2009/6/24 CN Yee <[email protected]>: > I think this is a very serious matter. It seems to me that the very philosophy > of Hibernate is making it uniquely unsuited for 3 tier architecture. I > wondered > why I have not came across any discussions regarding this all these years. ------------------------------------------------------------------------------ _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
