summaryrefslogtreecommitdiff
path: root/TAO/CIAO/docs/releasenotes/index.html
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/CIAO/docs/releasenotes/index.html')
-rw-r--r--TAO/CIAO/docs/releasenotes/index.html30
1 files changed, 15 insertions, 15 deletions
diff --git a/TAO/CIAO/docs/releasenotes/index.html b/TAO/CIAO/docs/releasenotes/index.html
index 324f1d83c77..0c4235aff1c 100644
--- a/TAO/CIAO/docs/releasenotes/index.html
+++ b/TAO/CIAO/docs/releasenotes/index.html
@@ -49,17 +49,17 @@ release</a> of <a href="http://www.dre.vanderbilt.edu/CIAO">CIAO</a>:
<CODE>$CIAO_ROOT/tools</CODE> that are missing in the DAnCE
implementation. Please see <a href="../TODO.html"> TODO </a> file
for more details. We plan to implement them soon and use DAnCE
- continuously.
+ continuously.
- <li> The first cut of DAnCE includes two parts:
+ <li> The first cut of DAnCE includes two parts:
<ul>
<li>
A modeling tool chain , <a href="http://www.dre.vanderbilt.edu/CoSMIC/">
- CoSMIC</a>, which is capable of describing the Assembly/Component
+ CoSMIC</a>, which is capable of describing the Assembly/Component
using <a
href="http://www.isis.vanderbilt.edu/Projects/gme/default.html">
GME</a> as the development bed. The artifacts generated from the
- CoSMIC are a set of XML descriptors.
+ CoSMIC are a set of XML descriptors.
<!-- Tao, I realy don't understand what this means - Bala -->
<li>This run-time infrastructure that performs the actual deployment
@@ -85,14 +85,14 @@ release</a> of <a href="http://www.dre.vanderbilt.edu/CIAO">CIAO</a>:
developers have to implement those operations within the
executor. We plan to get around this, i.e., users having to
implement these two operations, in the next month or so. <p>
-
+
<li>
-
+
Here is a set of updates in the CIDL Compiler.<p>
<ul>
<li>Fixed bugs in generation of inherited: home operations,
attribute operations, port operations, home factory operations,
- supported operations.<p>
+ supported operations.<p>
<li>Added support for multiplex uses ports. This implies that users
could use "uses multiple" in their component definitions. <p>
@@ -100,28 +100,28 @@ release</a> of <a href="http://www.dre.vanderbilt.edu/CIAO">CIAO</a>:
<li>Added automatic registration of value factories for event
consumers. This has been long outstanding. This change alleviates
component developers need to register the valuetype factory of their
- eventtypes with the ORB. <p>
+ eventtypes with the ORB. <p>
<li>Added support for emits keyword and we now generate navigation
code for this.<p>
<li>Fixed bug with multiple facets in a build that provide the same
interface.<p>
-
+
<li>Added option <code>--gen-exec-impl</code> to generate executor
impl classes, with no-op versions of each IDL operation.<p>
<li>Implemented get_all_facets() and get_all_consumers() navigation
methods.<p>
-
+
<li>Added support for the IDL keywords <code>setraises</code> and
<code>getraises</code>, associated with attributes in IDL3.<p>
-
+
<li>Added support for both subscription and event push of event types
that are a base class of the IDL-specified port type. A check is
performed during the subscribe call to make sure the eventtype is
actually an ancestor of the declared port type.<p>
-
+
<li>Problems with generated code when the composition declaration is
nested inside one or more IDL modules has prompted a change. The
'CIAO_GLUE_' prefix has been eliminated. The composition name is now
@@ -150,12 +150,12 @@ release</a> of <a href="http://www.dre.vanderbilt.edu/CIAO">CIAO</a>:
<li> The CIAO static configurator tool has been enhanced to support
processing of RTCORBA policy related information. Please see
ACE_wrappers/TAO/CIAO/docs/static_ciao_index.html.<p>
-
+
<li> To further interoperability with non-component-aware clients, there
- are files in the $CIAO_ROOT/tools/IDL3_to_IDL2 directory that can be
+ are files in the $CIAO_ROOT/tools/IDL3_to_IDL2 directory that can be
compiled into an executable called tao_idl3_to_idl2. This executable
takes an IDL file (on the command line) containing IDL3 declarations
- and outputs an IDL file with the IDL3 declarations converted to
+ and outputs an IDL file with the IDL3 declarations converted to
equivalent IDL2. IDL2 declarations in the input file are unchanged.
See the README file in that directory for more information.<p>