Hi jihnd, As far as I know, you shouldn't need to include any source files for server-side deployment. Although, I'm not completely familiar with Spring's RmiProxyFactoryBean or how you're going about integrating that into your GWT application, so please feel free to add some details if there's something I'm missing.
Hope that helps, -Sumit Chandel On Fri, Sep 26, 2008 at 9:27 PM, jihnd <[EMAIL PROTECTED]> wrote: > > hi all, > > i'm trying to build gwt into my app. currently i've got a spring > managed rmi service that is picked up and coded out through a servlet > and a refreshing html page > > i'd like to replace my front end with gwt, the question i have however > is regarding the neccessary inclusion of source code for the > serverside code, i need to include the spring class > RmiProxyFactoryBean - does this mean i have to package up the spring > source alongside the spring jars? it feels quite excessive?? > > i need spring because the whole app architecture including the > exporting of the object hat i want to display through gwt is built > with it, rmi is hte protocol that works, the httpinvoker doesn't... so > i'm locked into needing the RmiProxyFactoryBean to recieve the stub > and reserialize my object - therefore i can't think of anyway but > including spring source? > > any ideas be very much appeciated, thanks > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
