Lingo could enable asynchronous one way method calls on any method which returns void and throws no checked exceptions by default.

However this could confuse an existing Spring Remoting user. i.e. they may be expecting synchronous method invocation semantics having developed an application using either no remoting or using some other spring remoting implementation which only implements synchronous request-response and no asynchronous one ways.

So we have left asynchronous one ways disabled by default - unless the metadata strategy is configured to enable them or some metadata is used to explicitly enable asynchronous method calls.

Also see How do I enable async one ways