Spring's JmsInvokerProxyFactoryBean vs. Lingo's JmsProxyFactoryBean

[krause]

Does anybody know what is the difference between Spring's JmsInvokerProxyFactoryBean vs. Lingo's JmsProxyFactoryBean?
What about Spring's JmsInvokerServiceExporter vs. Lingo's JmsServiceExporter?
Is Lingo still relevant for JMS remoting in Spring in 2009 (Lingo doesn't seem to have much activity since 2006... or perhaps it has reached perfection)?

I'm still using Lingo's JmsProxyFactoryBean because I haven't been able to make Spring's JmsInvokerProxyFactoryBean to work in an asyncronous fashion. With Lingo you need to use a metadataStrategy property to make it asynchronous like so:

<bean id="asyncService" abstract="true"
     class="org.logicblaze.lingo.jms.JmsProxyFactoryBean">
        <property name="serviceInterface" value="org.xxx.Sample" />
        <property name="connectionFactory" ref="JmsConnectionFactory" />
            <property name="metadataStrategy">
                <bean class="org.logicblaze.lingo.SimpleMetadataStrategy">
                    <constructor-arg value="true" />
                </bean>
		</property>
	</bean>

How can I make Spring's JmsInvokerProxyFactoryBean asynchronous? I tried with the receiveTimeout property set to 1 (millisecond) and it sort of works asynchonously because an exception is thrown to the invoking code (the actual service keeps running ok)... but that is not exactly what I'm trying to achieve.

Any feedback would be more than welcome.

Some references I already checked out (all quite dated):

http://www.jroller.com/sjivan/entry/...allbacks_using
http://blog.springsource.com/category/jms/
http://forum.springsource.org/showthread.php?t=64560 (suggests that Spring integration might be the way to go)