In computing, Common Object Request Broker Architecture (CORBA), is a standard for software componentry. The CORBA standard is created and controlled by the Object Management Group (OMG). It defines APIs, communication protocol, and object/service information models to enable heterogeneous applications written in various languages running on various platforms to interoperate. CORBA therefore provides platform and location transparency for sharing well-defined objects across a distributed computing platform. In a general sense CORBA "wraps" code written in some language into a bundle containing additional information on the capabilities of the code inside, and how to call it. The resulting wrapped objects can then be called from other Computer programs (or CORBA objects) over the network. In this sense, CORBA can be considered as a machine-readable documentation format, similar to a header file but with considerably more information. CORBA uses an interface definition language (IDL) to specify the interfaces that objects will present to the world. CORBA then specifies a "mapping" from IDL to a specific implementation language like C plus plus or Java programming language. This mapping precisely describes how the CORBA data types are to be used in both client and server implementations. Standard mappings exist for Ada programming language, C language, C plus plus, Lisp programming language, Smalltalk, Java programming language, and Python programming language. There are also non-standard mappings for Perl and Tcl implemented by ORBs written for those languages. The CORBA IDL is only one example of an IDL. In addition to providing users with a language and a platform neutral remote procedure call specification, CORBA defines commonly needed services such as transactions and security. == CORBA Implementations == * [http://www.puder.org/corba/matrix/ An overview of available CORBA implementations] * [http://www.fpx.de/Combat/ Combat] A Tcl ORB, and a Tcl layer for C Plus Plus ORBs. * [http://www.prismtechnologies.com/section-item.asp?sid4=&sid3=&sid2=9&sid=18&id=174 e*ORB] - - A commercial ORB for Ada programming language, C programming language and C Plus Plus. * [http://www.jacorb.org/ JacORB] - - A Free Software (GNU Library General Public License) ORB implemented in Ada programming language. * [http://www.mico.org/ MICO] - - A Free Software (GNU General Public License) ORB implemented in C Plus Plus. * [http://omniorb.sourceforge.net/ omniORB] - - An Free Software (GNU Lesser General Public License) ORB for C Plus Plus and Python programming language. * [http://www.orbacus.com/ Orbacus] - commercial C Plus Plus ORB by IONA Technologies * [http://www.iona.com/products/orbix/welcome.htm Orbix] - commercial ORB by IONA Technologies * [http://sf.net/projects/perlorb/ Perl ORB] - - An Open Source (Artistic License) ORB implemented in Perl programming language. * PolyORB - - A Free Software (GNAT Modified General Public License) ORB implemented in Ada programming language. * [http://www.fnorb.org/ Python ORB] - - A Free Software (Python license) ORB implemented in Python programming language. * [http://www.sankhya.com/info/varadhi.html SANKHYA Varadhi] - - A commercial ORB for C Plus Plus * [http://www.cs.wustl.edu/~schmidt/TAO.html TAO] - - The Adaptive Communication Environment ORB, an Open Source ORB for C Plus Plus == See also == * Software componentry#Technologies for Software Components * Remote procedure call * Java remote method invocation * Web service * Distributed computing * Servant (CORBA) * Etherealization * Incarnation (CORBA) * Java 2 Platform, Enterprise Edition * GNOME Bonobo (computing) == References == *Thomas J. Mowbray, Raphael C. Malveau: ''CORBA Design Patterns'', John Wiley & Sons, ISBN 0-471-15882-8 *Robert Orfali: ''The Essential Client/Server Survival Guide'', John Wiley & Sons, ISBN 0-471-15325-7 *Robert Orfali, Dan Harkey, Jeri Edwards: ''The Essential Distributed Objects Survival Guide'', John Wiley & Sons, ISBN 0-471-12993-3 *Robert Orfali, Dan Harkey: ''Client/Server Programming with JAVA and CORBA'', John Wiley & Sons, ISBN 0-471-24578-X *Michi Henning, Steve Vinoski: ''Advanced CORBA Programming with C++'', Addison-Wesley, ISBN 0-201-37927-9 *Axel Korthaus, Martin Schader, Markus Aleksy: [http://www.wifo.uni-mannheim.de/CORBA/''Implementing Distributed Systems with Java and CORBA''], Springer, ISBN 3-540-24173-6 *Fintan Bolton: ''Pure Corba'', Sams Publishing, ISBN 0-672-31812-1 *Jon Siegel: ''CORBA 3 - Fundamentals and Programming'', John Wiley & Sons, ISBN 0-471-29518-3 *Ron Zahavi: ''Enterprise Application Integration with CORBA: Component and Web-Based Solutions'', John Wiley & Sons, ISBN 0-471-32720-4 *Bret Hartman, Konstantin Beznosov, Steve Vinoski, Donald Flinn: ''Enterprise Security with EJB and CORBA'', John Wiley & Sons, ISBN 0-471-40131-5 *Thomas J. Mowbray, Ron Zahavi: ''The Essential Corba: System Integration Using Distributed Objects'', John Wiley & Sons, ISBN 0-471-10611-9 *Michael Rosen, David Curtis: ''Integrating CORBA and COM Applications'', John Wiley & Sons, ISBN 0-471-19827-7 *Gerald Brose, Andreas Vogel, Keith Duddy: ''Java Programming with CORBA'', John Wiley & Sons, ISBN 0-471-37681-7 *John Schettino, Robin S. Hohman, Liz O'Hara: ''CORBA For Dummies'', Hungry Minds, ISBN 0-764-50308-1 *Jeremy L. Rosenberger: ''Teach Yourself CORBA in 14 Days'', Sams Publishing, ISBN 0-672-31208-5 *Jon Siegel: ''Quick CORBA 3'', John Wiley & Sons, ISBN 0-471-38935-8 *Robert Orfali, Dan Harkey, Jeri Edwards: ''Instant CORBA'', John Wiley & Sons, ISBN 0-471-18333-4 *Paul Harmon, William Morrissey: ''The Object Technology Casebook'', John Wiley & Sons, ISBN 0-471-14717-6 == External links == * [http://www.omg.org/technology/documents/formal/corba_2.htm OMG CORBA 3] * [http://www.omg.org/ Object Management Group] * [http://www.corba.org/ Information Board] * [http://www.omg.org/technology/documents/spec_catalog.htm Catalog of OMG Specifications] ** [http://www.omg.org/technology/documents/idl2x_spec_catalog.htm IDL / Language Mapping] ** [http://www.omg.org/technology/documents/corba_spec_catalog.htm#ccm CORBA Component Model (CCM)] ** [http://www.omg.org/technology/documents/corba_spec_catalog.htm IIOP] ** [http://www.omg.org/technology/documents/corbaservices_spec_catalog.htm Services] ** [http://www.omg.org/technology/documents/corbafacilities_spec_catalog.htm Facilities] ** [http://www.omg.org/technology/documents/domain_spec_catalog.htm Domain] ** [http://www.omg.org/technology/documents/embed_intel_spec_catalog.htm Embedded Intelligence] ** [http://www.omg.org/technology/documents/formal/omg_security.htm Security] ** [http://www.omg.org/technology/documents/modeling_spec_catalog.htm UML, MOF, XMI, CWM] * [http://cbbrowne.com/info/corba.html Description] by Christopher B. Browne * [http://corbaconf.kiev.ua/ CORBA support for autoconf] * [news:comp.object.corba discussions] Object-oriented programming Acronyms
Modification note (7/1/2003) I just thought I'd clear this up to avoid a mod-war. IDL stands for Interface Definition Language, *not* Interface "Description" Language. It was recently changed incorrectly to the latter. I've put it back the way that it was. See the CORBA spec p 3-1. (Derek) I noticed that someone broke my change above when doing some edits. I've re-edited it so that it is now correct once more. (Derek) == CORBA/Common object request broker architecture == User:68.167.249.197 23:44, 7 Apr 2004 (UTC): I'd suggest that it is standard practice to have the main article body for CORBA/Common object request broker architecture to be under the fully expanded version of the name (cf. Remote procedure call/RPC, and File transfer protocol/FTP to name two examples). :That's right! User:I am sexy 23:46, 7 Apr 2004 (UTC) :I would argue that File transfer protocol should be moved to FTP, though Remote procedure call should stay as it is. This is because there is not just one file transfer protocol. Having a page title like "File transfer protocol" or "Common object request broker architecture" implies that there is more than one - for example - "a file transfer protocol is..." or "a common object request broker architecture", whilst "an FTP" or "a CORBA" is less appropriate. User:Dysprosia 06:40, 8 Apr 2004 (UTC) ::User:68.167.249.2 09:02, 8 Apr 2004 (UTC): Admittedly "file transfer protocol" can be generically used, but I disagree about "common object request broker architecture" which has established itself as a specific standard. That is emphasized outside of wikipedia by capitalizing all the words. Additional examples, like OSI, DNS, SNMP, LAN, FDDI, SMTP, ICMP, RARP all redirect to the full words, though HTTP doesn't. == an exception proving the rule; disambig COBRA and CORBA == User:68.167.249.197 00:03, 8 Apr 2004 (UTC): One good standard practice within wikipedia is to not disambiguate misspellings. I agree that this is a good guideline to follow. As I also note at Talk:COBRA, I would contend that COBRA vs. CORBA is a case where the exception proves the rule. This is a case of two five-letter acronyms, which is unusual. For two acronyms of that length (and, to get perhaps overly analytical about it, the fact that B and R are both typed by the left index finger on a QWERTY keyboard), isn't a reasonable to anticipate our audience would appreciate such a disambiguation here? I would never advocate disambiguation for TLAs. but this seems a case where a good rule has a reasonable exception. :User:68.167.249.2 09:02, 8 Apr 2004 (UTC): User:Dysprosia's suggestion elsewhere of a disambiguation block prefacing the CORBA page seems like the best of both worlds to resolve this. == Images? == Hi. What are these supposed to indicate? Why are they not defined? Thanks. --User:ChrisRuvolo 01:53, 6 Apr 2005 (UTC) : Developmant Status. In researching the links I found project which are not fully developed and/or which have not been updated for many years. With the % rating on what to expect when following the link. If you know the project and find the rating unfair you are free to correct - just be honest - a project with barely make minimum feature set and has seen no update for 3 years should not be marked 100%. --User:Krischik 06:49, 6 Apr 2005 (UTC) ::Ok, thanks for the info. I don't mind their use, but in the article it should be defined what they represent.. and then what the various implementations are lacking (justification of each 50% rating for example). They won't be able to be interpreted usefully otherwise. --User:ChrisRuvolo 16:23, 6 Apr 2005 (UTC)
#REDIRECT CORBA
See other meanings of words starting from letter:
Words begining with CORBA:
CORBA
CORBA
Corba
CorbaScript
CorbaScript
CORBA_architecture
CORBA_Component_Model
CORBA
In computing, Common Object Request Broker Architecture (CORBA), is a standard for software componentry. The CORBA standard is created and controlled by the Object Management Group (OMG). It defines APIs, communication protocol, and object/service information models to enable heterogeneous applications written in various languages running on various platforms to interoperate. CORBA therefore provides platform and location transparency for sharing well-defined objects across a distributed computing platform. In a general sense CORBA "wraps" code written in some language into a bundle containing additional information on the capabilities of the code inside, and how to call it. The resulting wrapped objects can then be called from other Computer programs (or CORBA objects) over the network. In this sense, CORBA can be considered as a machine-readable documentation format, similar to a header file but with considerably more information. CORBA uses an interface definition language (IDL) to specify the interfaces that objects will present to the world. CORBA then specifies a "mapping" from IDL to a specific implementation language like C plus plus or Java programming language. This mapping precisely describes how the CORBA data types are to be used in both client and server implementations. Standard mappings exist for Ada programming language, C language, C plus plus, Lisp programming language, Smalltalk, Java programming language, and Python programming language. There are also non-standard mappings for Perl and Tcl implemented by ORBs written for those languages. The CORBA IDL is only one example of an IDL. In addition to providing users with a language and a platform neutral remote procedure call specification, CORBA defines commonly needed services such as transactions and security. == CORBA Implementations == * [http://www.puder.org/corba/matrix/ An overview of available CORBA implementations] * [http://www.fpx.de/Combat/ Combat] A Tcl ORB, and a Tcl layer for C Plus Plus ORBs. * [http://www.prismtechnologies.com/section-item.asp?sid4=&sid3=&sid2=9&sid=18&id=174 e*ORB] - - A commercial ORB for Ada programming language, C programming language and C Plus Plus. * [http://www.jacorb.org/ JacORB] - - A Free Software (GNU Library General Public License) ORB implemented in Ada programming language. * [http://www.mico.org/ MICO] - - A Free Software (GNU General Public License) ORB implemented in C Plus Plus. * [http://omniorb.sourceforge.net/ omniORB] - - An Free Software (GNU Lesser General Public License) ORB for C Plus Plus and Python programming language. * [http://www.orbacus.com/ Orbacus] - commercial C Plus Plus ORB by IONA Technologies * [http://www.iona.com/products/orbix/welcome.htm Orbix] - commercial ORB by IONA Technologies * [http://sf.net/projects/perlorb/ Perl ORB] - - An Open Source (Artistic License) ORB implemented in Perl programming language. * PolyORB - - A Free Software (GNAT Modified General Public License) ORB implemented in Ada programming language. * [http://www.fnorb.org/ Python ORB] - - A Free Software (Python license) ORB implemented in Python programming language. * [http://www.sankhya.com/info/varadhi.html SANKHYA Varadhi] - - A commercial ORB for C Plus Plus * [http://www.cs.wustl.edu/~schmidt/TAO.html TAO] - - The Adaptive Communication Environment ORB, an Open Source ORB for C Plus Plus == See also == * Software componentry#Technologies for Software Components * Remote procedure call * Java remote method invocation * Web service * Distributed computing * Servant (CORBA) * Etherealization * Incarnation (CORBA) * Java 2 Platform, Enterprise Edition * GNOME Bonobo (computing) == References == *Thomas J. Mowbray, Raphael C. Malveau: ''CORBA Design Patterns'', John Wiley & Sons, ISBN 0-471-15882-8 *Robert Orfali: ''The Essential Client/Server Survival Guide'', John Wiley & Sons, ISBN 0-471-15325-7 *Robert Orfali, Dan Harkey, Jeri Edwards: ''The Essential Distributed Objects Survival Guide'', John Wiley & Sons, ISBN 0-471-12993-3 *Robert Orfali, Dan Harkey: ''Client/Server Programming with JAVA and CORBA'', John Wiley & Sons, ISBN 0-471-24578-X *Michi Henning, Steve Vinoski: ''Advanced CORBA Programming with C++'', Addison-Wesley, ISBN 0-201-37927-9 *Axel Korthaus, Martin Schader, Markus Aleksy: [http://www.wifo.uni-mannheim.de/CORBA/''Implementing Distributed Systems with Java and CORBA''], Springer, ISBN 3-540-24173-6 *Fintan Bolton: ''Pure Corba'', Sams Publishing, ISBN 0-672-31812-1 *Jon Siegel: ''CORBA 3 - Fundamentals and Programming'', John Wiley & Sons, ISBN 0-471-29518-3 *Ron Zahavi: ''Enterprise Application Integration with CORBA: Component and Web-Based Solutions'', John Wiley & Sons, ISBN 0-471-32720-4 *Bret Hartman, Konstantin Beznosov, Steve Vinoski, Donald Flinn: ''Enterprise Security with EJB and CORBA'', John Wiley & Sons, ISBN 0-471-40131-5 *Thomas J. Mowbray, Ron Zahavi: ''The Essential Corba: System Integration Using Distributed Objects'', John Wiley & Sons, ISBN 0-471-10611-9 *Michael Rosen, David Curtis: ''Integrating CORBA and COM Applications'', John Wiley & Sons, ISBN 0-471-19827-7 *Gerald Brose, Andreas Vogel, Keith Duddy: ''Java Programming with CORBA'', John Wiley & Sons, ISBN 0-471-37681-7 *John Schettino, Robin S. Hohman, Liz O'Hara: ''CORBA For Dummies'', Hungry Minds, ISBN 0-764-50308-1 *Jeremy L. Rosenberger: ''Teach Yourself CORBA in 14 Days'', Sams Publishing, ISBN 0-672-31208-5 *Jon Siegel: ''Quick CORBA 3'', John Wiley & Sons, ISBN 0-471-38935-8 *Robert Orfali, Dan Harkey, Jeri Edwards: ''Instant CORBA'', John Wiley & Sons, ISBN 0-471-18333-4 *Paul Harmon, William Morrissey: ''The Object Technology Casebook'', John Wiley & Sons, ISBN 0-471-14717-6 == External links == * [http://www.omg.org/technology/documents/formal/corba_2.htm OMG CORBA 3] * [http://www.omg.org/ Object Management Group] * [http://www.corba.org/ Information Board] * [http://www.omg.org/technology/documents/spec_catalog.htm Catalog of OMG Specifications] ** [http://www.omg.org/technology/documents/idl2x_spec_catalog.htm IDL / Language Mapping] ** [http://www.omg.org/technology/documents/corba_spec_catalog.htm#ccm CORBA Component Model (CCM)] ** [http://www.omg.org/technology/documents/corba_spec_catalog.htm IIOP] ** [http://www.omg.org/technology/documents/corbaservices_spec_catalog.htm Services] ** [http://www.omg.org/technology/documents/corbafacilities_spec_catalog.htm Facilities] ** [http://www.omg.org/technology/documents/domain_spec_catalog.htm Domain] ** [http://www.omg.org/technology/documents/embed_intel_spec_catalog.htm Embedded Intelligence] ** [http://www.omg.org/technology/documents/formal/omg_security.htm Security] ** [http://www.omg.org/technology/documents/modeling_spec_catalog.htm UML, MOF, XMI, CWM] * [http://cbbrowne.com/info/corba.html Description] by Christopher B. Browne * [http://corbaconf.kiev.ua/ CORBA support for autoconf] * [news:comp.object.corba discussions] Object-oriented programming Acronyms
CORBA
Modification note (7/1/2003) I just thought I'd clear this up to avoid a mod-war. IDL stands for Interface Definition Language, *not* Interface "Description" Language. It was recently changed incorrectly to the latter. I've put it back the way that it was. See the CORBA spec p 3-1. (Derek) I noticed that someone broke my change above when doing some edits. I've re-edited it so that it is now correct once more. (Derek) == CORBA/Common object request broker architecture == User:68.167.249.197 23:44, 7 Apr 2004 (UTC): I'd suggest that it is standard practice to have the main article body for CORBA/Common object request broker architecture to be under the fully expanded version of the name (cf. Remote procedure call/RPC, and File transfer protocol/FTP to name two examples). :That's right! User:I am sexy 23:46, 7 Apr 2004 (UTC) :I would argue that File transfer protocol should be moved to FTP, though Remote procedure call should stay as it is. This is because there is not just one file transfer protocol. Having a page title like "File transfer protocol" or "Common object request broker architecture" implies that there is more than one - for example - "a file transfer protocol is..." or "a common object request broker architecture", whilst "an FTP" or "a CORBA" is less appropriate. User:Dysprosia 06:40, 8 Apr 2004 (UTC) ::User:68.167.249.2 09:02, 8 Apr 2004 (UTC): Admittedly "file transfer protocol" can be generically used, but I disagree about "common object request broker architecture" which has established itself as a specific standard. That is emphasized outside of wikipedia by capitalizing all the words. Additional examples, like OSI, DNS, SNMP, LAN, FDDI, SMTP, ICMP, RARP all redirect to the full words, though HTTP doesn't. == an exception proving the rule; disambig COBRA and CORBA == User:68.167.249.197 00:03, 8 Apr 2004 (UTC): One good standard practice within wikipedia is to not disambiguate misspellings. I agree that this is a good guideline to follow. As I also note at Talk:COBRA, I would contend that COBRA vs. CORBA is a case where the exception proves the rule. This is a case of two five-letter acronyms, which is unusual. For two acronyms of that length (and, to get perhaps overly analytical about it, the fact that B and R are both typed by the left index finger on a QWERTY keyboard), isn't a reasonable to anticipate our audience would appreciate such a disambiguation here? I would never advocate disambiguation for TLAs. but this seems a case where a good rule has a reasonable exception. :User:68.167.249.2 09:02, 8 Apr 2004 (UTC): User:Dysprosia's suggestion elsewhere of a disambiguation block prefacing the CORBA page seems like the best of both worlds to resolve this. == Images? == Hi. What are these supposed to indicate? Why are they not defined? Thanks. --User:ChrisRuvolo 01:53, 6 Apr 2005 (UTC) : Developmant Status. In researching the links I found project which are not fully developed and/or which have not been updated for many years. With the % rating on what to expect when following the link. If you know the project and find the rating unfair you are free to correct - just be honest - a project with barely make minimum feature set and has seen no update for 3 years should not be marked 100%. --User:Krischik 06:49, 6 Apr 2005 (UTC) ::Ok, thanks for the info. I don't mind their use, but in the article it should be defined what they represent.. and then what the various implementations are lacking (justification of each 50% rating for example). They won't be able to be interpreted usefully otherwise. --User:ChrisRuvolo 16:23, 6 Apr 2005 (UTC)
Corba
#REDIRECT CORBA
See other meanings of words starting from letter:
C
CA | CB | CD | CE | CF | CG | CH | CI | CJ | CK | CL | CM | CN | CO | CP | CR | CS | CT | CU | CW | CX | CY | CZ |Words begining with CORBA:
CORBA
CORBA
Corba
CorbaScript
CorbaScript
CORBA_architecture
CORBA_Component_Model
Sponsored links: praca, nurkowanie.
These materials are based on Wikipedia and licensed under the GNU FDL
YouTube.com videos better site than Turbo Tax 2007
