Hi,
We are looking for arguments for using technologies that allows .NET
Framework and Java to interoperate on a point to point basis.
The two options are XML Web Services and .NET Remoting with using third
party runtimebridges likes Ja.NET and JNBridgePro.
.NET Remoting technology provides greater performance then Web Services
in a pure .NET Framework environment. But Web Services provides more
freedom from having to dsescribe methods explicitly.
I like to hear experience in using thes two interoperability
technologies.
Best regards
John
References:
Interoperability Technologies: Point to Point
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/jdni
_ch01.asp
Michael Nemtsev - 14 Nov 2006 18:41 GMT
Hello JohnK,
J> We are looking for arguments for using technologies that allows .NET
J> Framework and Java to interoperate on a point to point basis.
J> The two options are XML Web Services and .NET Remoting with using
J> third party runtimebridges likes Ja.NET and JNBridgePro.
J> .NET Remoting technology provides greater performance
Not always, comparing performance I'd say that WebServices beat Remoting
in number of cases
See there http://msdn2.microsoft.com/en-us/library/ms996381.aspx
J> then Web Services in a pure .NET Framework environment.
There is nothing common with WebServices. WS is the mean of interoperability,
not the specific MS technology.
See the WS on the w3c http://www.w3.org/2002/ws/
J> But Web Services provides more freedom from having to describe methods
explicitly.
J> I like to hear experience in using thes two interoperability
J> technologies.
I suggest u to use WebServices. It's reasonable choice for the interoperability
among components and in cross-platforms systems.
The weak of remoting is no support for declarative extention.
---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour
"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche