Component Object Model – link to JavaBeans

It is not possible to add the new link because it would replace an existing, longer link.

Line 43: Line 43:
Over time, COM is being replaced with other technologies such as [[.NET Framework|Microsoft .NET]] and [[web services]] (i.e. via [[Windows communication foundation|WCF]]). However, COM objects can be used in a .NET language via [[COM Interop]].
Over time, COM is being replaced with other technologies such as [[.NET Framework|Microsoft .NET]] and [[web services]] (i.e. via [[Windows communication foundation|WCF]]). However, COM objects can be used in a .NET language via [[COM Interop]].


COM is similar to other component technologies such as [[IBM System Object Model|SOM]], [[CORBA]] and [[Enterprise JavaBeans]], although each has its strengths and weaknesses.
COM is similar to other component technologies such as [[IBM System Object Model|SOM]], [[CORBA]] and Enterprise [[JavaBeans]], although each has its strengths and weaknesses.


Unlike [[C++]], COM provides a stable [[application binary interface]] (ABI) that is unaffected by compiler differences.<ref>Microsoft forum: [https://archive.today/20130216110824/http://social.msdn.microsoft.com/Forums/en/vcgeneral/thread/86eda6a7-4d90-4e19-a9d4-6cbe22b661f4 Binary compatibility across Visual C++ versions]</ref> This makes using COM advantageous for object-oriented C++ libraries that are to be used by clients compiled via different compilers.
Unlike [[C++]], COM provides a stable [[application binary interface]] (ABI) that is unaffected by compiler differences.<ref>Microsoft forum: [https://archive.today/20130216110824/http://social.msdn.microsoft.com/Forums/en/vcgeneral/thread/86eda6a7-4d90-4e19-a9d4-6cbe22b661f4 Binary compatibility across Visual C++ versions]</ref> This makes using COM advantageous for object-oriented C++ libraries that are to be used by clients compiled via different compilers.