Seems pretty intuitive to work with.
How hard would it be to have a deployer for the .NET App.config such that JBoss services are visible in C# clients as native C# interfaces?
Example of the App.config server configuration XML:
<?xml version="1.0" encoding="utf?8" ?> <configuration> <system.runtime.remoting> <application> <channels> <channel ref="http" port="6007"> <serverProviders> <provider ref="wsdl" /> <formatter ref="soap" typeFilterLevel="Full" /> <formatter ref="binary" typeFilterLevel="Full" /> </serverProviders> <clientProviders> <formatter ref="binary" /> </clientProviders> </channel> </channels> <service> <wellknown type="SharedCode.Chatter, SharedCode" objectUri="Chatter.soap" mode="Singleton" /> </service> </application> </system.runtime.remoting> </configuration>
Could probably cobble this together to make it so would work over remoting. I don't know much about the MS stuff, so can't say for sure.
However, my biggest concern would be cases other than simple invocations. For example, invocations wiht complex parameters or return types. The mappings are usually what makes this most difficult (even with just plain SOAP).