In computer programming, and particularly in Microsoft Windows programming, third party software component refers to a reusable software component developed to be either freely distributed or sold by an entity other than the original vendor of the development platform.
MicrosoftVisual Basic spawned the first commercially viable market for reusable software components. Visual Basic's first extensibility mechanism was the specification for VBX custom controls.
In version 4.0 of Visual Basic, the OCX custom control was introduced to replace VBX. OCX was later renamed ActiveX and then COM. In version 7.0 of Visual Basic, also known as VB.NET, Microsoft introduced the .NET Component to replace both VBX and ActiveX. It was still possible to use many ActiveX components in VB.NET by wrapping them in a .NET layer.
The Component Vendor Consortium (CVC) (http://www.components.org/) is a not for profit industry association dedicated to supporting organizations and developers building components and tools for the professional Windows developer.
Conceptually, a wrapper is an additional layer of software meant to encase a component and allow access to the input to and output from that component.
Use of this approach can allow for new possibilities in the testing of 3rdpartysoftwarecomponents for which source code is unavailable.
However, attempting to actually implement wrappers for Java classes as separate layers of software is not as straight forward as it seems.