Comments on: Spring XmlRpcServiceExporter http://blog.springsource.com/arjen/archives/2005/02/12/spring-xmlrpcserviceexporter/ A blog about programming in .NET and Java Wed, 07 Jan 2009 01:52:59 +0000 http://wordpress.org/?v=2.0.2 by: Arjen http://blog.springsource.com/arjen/archives/2005/02/12/spring-xmlrpcserviceexporter/#comment-246 Fri, 29 Jul 2005 13:26:00 +0000 http://blog.springsource.com/arjen/archives/2005/02/12/spring-xmlrpcserviceexporter/#comment-246 You would configure it like any other <code>RemoteExporter</code>. Refer to the <a href="http://static.springframework.org/spring/docs/1.2.x/reference/remoting.html#d0e11537">Spring Reference documentation on remoting</a> for more info. You would configure it like any other RemoteExporter. Refer to the Spring Reference documentation on remoting for more info.

]]> by: Steve Daly http://blog.springsource.com/arjen/archives/2005/02/12/spring-xmlrpcserviceexporter/#comment-243 Wed, 27 Jul 2005 16:56:22 +0000 http://blog.springsource.com/arjen/archives/2005/02/12/spring-xmlrpcserviceexporter/#comment-243 Can you post an example of how to configure this exporter with a service in the application context config file? TIA, Steve Can you post an example of how to configure this exporter with a service in the application context config file?

TIA,

Steve

]]> by: Alef http://blog.springsource.com/arjen/archives/2005/02/12/spring-xmlrpcserviceexporter/#comment-31 Sun, 13 Feb 2005 22:53:32 +0000 http://blog.springsource.com/arjen/archives/2005/02/12/spring-xmlrpcserviceexporter/#comment-31 Well, like I said in my mail already, it's gonna be hard to get full serializability for all your arguments. Normale beans and arrays work, but once you start to use collections, you can't transform the structs into the necessary objects anymore (there's not type information available). Then there's properties that expose interfaces. You can go and guess a concrete type there. Finally there's the objects that don't adhere to the JavaBeans spec. You'll need property editors for those, but that's something I think you don't want since you want to have completely transparent RPC. Well, on the other side, it works for simple beans. I think we'll have to add this to the Spring sandbox soon. Well, like I said in my mail already, it’s gonna be hard to get full serializability for all your arguments. Normale beans and arrays work, but once you start to use collections, you can’t transform the structs into the necessary objects anymore (there’s not type information available). Then there’s properties that expose interfaces. You can go and guess a concrete type there. Finally there’s the objects that don’t adhere to the JavaBeans spec. You’ll need property editors for those, but that’s something I think you don’t want since you want to have completely transparent RPC.

Well, on the other side, it works for simple beans. I think we’ll have to add this to the Spring sandbox soon.

]]>