New CORBA 3.0 and CCM 3.0 specs
[Posted August 14, 2002 by cook]
| From: |
| Karel Gardas <kgardas@objectsecurity.com> |
| To: |
| lwn@lwn.net |
| Subject: |
| CORBA 3.0 announcement in development section. |
| Date: |
| Wed, 14 Aug 2002 20:25:56 +0200 (CEST) |
Hello,
I think it would be worth the place to announce new CORBA 3.0 and CCM
3.0 specifications in 'Development' section of LWN. Unfortunately I
don't know who is responsible for this section and so I'm sending
this email directly to you in the hope that it'll find the right way.
In case of any problem with this text, please contact me.
Thanks,
Karel
CORBA 3.0 brings core changes to the CORBA which are required by new
CORBA Component Model (CCM). From this point of view we can compare
this specification with CORBA 2.0 specification which brought new
GIOP/IIOP protocols which allow CORBA vendors products to
interoperate on the wire. This was in 1995 and from this time whole
CORBA ride out long way. Now CORBA 3.0 allows CORBA application
developers to use component framework which from design point of view
doesn't have competition in the market. There is nothing except CCM
which brings ability to write/deploy/use components in language,
operating systems and vendors independent way.
CORBA 3.0 specification contains a lot of core changes, but the most
visible are these required by CORBA Component Model. CCM as a whole
is separated specification and specifies these main building blocks:
- Component Model
- OMG CIDL Syntax and Semantics
- CCM Implementation framework
- The Container Programming Model
- Integration with Enterprise JavaBeans
- Packaging and Deployment
The CCM specification defines two compliant levels: basic and
extended. The basic level is very similar to Enterprise JavaBeans
from functionality point of view, but note that such components don't
need to be implemented in Java, but also in other programming
languages. The extended model provides all features and power of
whole CORBA Component Framework. By using it the developers will be
able to define all necessary interfaces, composition and persistent
types using two declarative languages: Extended CORBA Interface
Definition Language (IDL) and newly introduced Component
Implementation Definition Language (CIDL). The goal is to write as
much as possible in these languages and let IDL/CIDL compilers do the
whole job except implementation of so called business logic, or
business operations, which is duty of application developer and which
has to be done in certain programming language.
The first draft of CCM appears on the net in autumn 1999 and so it
was really a long way to the final specification, but I hope it was
worth the time.
------
Note that this paragraph could contains some trademarks, for example
CORBA, IDL, CIDL, CCM are trademarks of Object Management Group (OMG)
- software consortium which writes CORBA and many other specifications.
--
Karel Gardas kgardas@objectsecurity.com
ObjectSecurity Ltd. http://www.objectsecurity.com
(
Log in to post comments)