Hi, sounds pretty much like our architecture, except we are using CORBA instead of RMI (corba is faster).
Since RMI is pretty tied to java I would strongly encourage you to write a java-file generator, which generates a facade on top of the rmi interfaces, hiding error handling and de/marshaling from the services implementations and the clients. IMO there is no such generator yet (publicly) available, at least no such generator which is good. But if you have some good coders, I wrote the first version of our generator (based on class file parsing and unfortunately not public) in 3 days, and further 10 days were invested before launch. We are absolutely happy having such a generator, because, combined with a MetaFactory concept/pattern, it gives you absolute flexibility for development and good injection points for monitoring, security and debug. Instead of class-file-based generation you could also use the doclet-driven generation, albeit its a bit slower (a company where a friend of mine works just abandoned doclet-driven generation, but they have to generate 1.000.000 lines of code...). Your struts-related code should never see anything behind your generated meta-enterprise, this way you'll keep all options open. regards Leon On 6/15/06, George Papandreou <[EMAIL PROTECTED]> wrote:
Hello All, we need to integrate our Struts application with an RMI server. But we don't know whether tapping into this RMI server (not EJB) would be an easy thing to achieve and we have limited time to investigate. Has any one faced a similar situation to this? Do we need to provide a client side abstraction framework to enable marshalling/handling of these remote serializable objects? If this is true is anyone aware of any software we can use? Many thanks for reading this, George.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]