Oh, duh the Service Locator pattern. :-) Yes I had planned on using something to do the job of a Singleton (and finding it). JNDI is too heavyweight when everything is located on the client (except for the database and a few ancilary web services) and I wasn't sure if it was safe to just use a singleton and hand out a references of the sole application context to every stinkin thread in the app.
No service locator was generated in my code. I must be doing something wrong in andromda.xml. I'll look into it. I don't know a thing about spring's remoting capabilities. As it stands I was going to leave 90% of the code on the client because I don't want to use EJB. _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1683#1683 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
