ok i see what you are saying. the business logic is *physically* in the presentation as in bundled in the rich-client, however *logically* in the design and actual package namespace it is clearly seperated. I am using controller classes in the domain that maintain complex business logic so it's not as if i couldn't just later have those become remote services via rmi, at this stage i'm just trying to understand what i would gain by making those remote and running them in an application server. i'm already getting transaction support from spring and hibernate. what other pro's are there to remoting the business objects?
i will probably have a copy of the business code running on the server at some point for some web services (unrelated to the rich-client) but still that code will be identical to the business code on the client, so does that really complicate things that much? what is the impetus behind your logic? performance, scalability, design? thanks for all of your help. apologies for being so dense. _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1714#1714 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
