|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Steve Vinoski, "Java Business Integration," IEEE Internet Computing, vol. 9, no. 4, pp. 89-91, July/August, 2005. | |||
| BibTex | x | ||
| @article{ 10.1109/MIC.2005.86, author = {Steve Vinoski}, title = {Java Business Integration}, journal ={IEEE Internet Computing}, volume = {9}, number = {4}, issn = {1089-7801}, year = {2005}, pages = {89-91}, doi = {http://doi.ieeecomputersociety.org/10.1109/MIC.2005.86}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Internet Computing TI - Java Business Integration IS - 4 SN - 1089-7801 SP89 EP91 EPD - 89-91 A1 - Steve Vinoski, PY - 2005 VL - 9 JA - IEEE Internet Computing ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MIC.2005.86
An argument has been making the rounds in distributed computing circles about how best to define interfaces for distributed elements. Some advocate the use of an interface definition language (IDL), whereas others prefer to use programming languages directly. The Java Business Integration (JBI) specification reverses the Java community's historical preference for the latter and chooses a reasonable middle ground.
Citation:
Steve Vinoski, "Java Business Integration," IEEE Internet Computing, vol. 9, no. 4, pp. 89-91, July-Aug. 2005, doi:10.1109/MIC.2005.86
Usage of this product signifies your acceptance of the Terms of Use.

