Ok thanks. I think being a spring newbie is leading me to make some dumb decisions. I guess I had made some assumptions based upon my experience with multi-tier java apps from a few years ago. I was afraid of using big chunky EJB entities (oh the horrors of EJB circa 2000) when my client machines are fast with lots of ram and can handle talking to the database themselves (through hibernate). I was planning on using a second-level federated cache for hibernate to help ease the database load. it's a good thing this is all a proof of concept right now. :-)
i'll check out spring's remoting and see if it doesn't add too much complexity to the code. thankfully i don't have to worry about having a big fat Rich-Client because i have a big fat rich client (as far as hardware goes). :-) _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1685#1685 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
