what we wanted to do is to expose a hessian-remoted service as flex destination. i suppose that's not the behavior ever expected from *ProxyFactoryBean classes (same for Hessian, HttpInvoker and RMI), but anyway.
please don't question why . we just want to do it.
when RemotingDestinationExporter of spring-flex tries to create a flex destination for already remoted service it throws NPE when trying to determine targetClass. that apparently happens because all remote proxies have EmptyTargetSource as target source.
so i wonder if that can be considered a bug in spring-remoting, or it's just inappropriate use and we'll have to fix it ourselves ?