[omniORB] TypeCodes, tk_alias, OmniORB, and JacORB
Monceaux, Weston P ERDC-ITL-MS Contractor
Weston.P.Monceaux@erdc.usace.army.mil
Thu, 7 Dec 2000 09:15:47 -0600
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C06060.961B5738
Content-Type: text/plain;
charset="iso-8859-1"
> -----Original Message-----
> From: Duncan Grisby [mailto:dgrisby@uk.research.att.com]
> Sent: Thursday, December 07, 2000 08:09
> To: Monceaux, Weston P ERDC-ITL-MS Contractor
> Cc: omniorb-list@uk.research.att.com
> Subject: Re: [omniORB] TypeCodes, tk_alias, OmniORB, and JacORB
>
>
> On Monday 4 December, "Monceaux, Weston P ERDC-ITL-MS
> Contractor" wrote:
>
> > Apologies for the HTML.
>
> You are still sending HTML...
Sorry again. This message probably has HTML in it as well even though every
option in Outlook <insert derogatory comment here> is set to NOT send HTML.
So this will be my last post until I locate a better mail client to spare
everyone of my HTML :-)
Concerning the problem I was reporting, it has been resolved. Turns out
that OmniORB and JacORB were doing everything correctly when handling
TypeCodes and Anys (which I figured must have been the case, otherwise lots
of other complaints would have been seen by now). The problem was a bug in
the JacORB IDL compiler generating incorrect TypeCode information under
certain conditions. I notified the maintainers of JacORB, and it turns out
they had already found and fixed the problem. For anyone interested, they
have a fix on the "Known Problems" section of their website.
Thanks again for the help.
Weston Monceaux
------_=_NextPart_001_01C06060.961B5738
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2448.0">
<TITLE>RE: [omniORB] TypeCodes, tk_alias, OmniORB, and JacORB </TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>> -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>> From: Duncan Grisby [<A =
HREF=3D"mailto:dgrisby@uk.research.att.com">mailto:dgrisby@uk.research.a=
tt.com</A>]</FONT>
<BR><FONT SIZE=3D2>> Sent: Thursday, December 07, 2000 08:09</FONT>
<BR><FONT SIZE=3D2>> To: Monceaux, Weston P ERDC-ITL-MS =
Contractor</FONT>
<BR><FONT SIZE=3D2>> Cc: omniorb-list@uk.research.att.com</FONT>
<BR><FONT SIZE=3D2>> Subject: Re: [omniORB] TypeCodes, tk_alias, =
OmniORB, and JacORB</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> On Monday 4 December, "Monceaux, Weston P =
ERDC-ITL-MS</FONT>
<BR><FONT SIZE=3D2>> Contractor" wrote:</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> > Apologies for the HTML.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> You are still sending HTML...</FONT>
</P>
<P><FONT SIZE=3D2>Sorry again. This message probably has HTML in =
it as well even though every option in Outlook <insert derogatory =
comment here> is set to NOT send HTML. So this will be my last =
post until I locate a better mail client to spare everyone of my HTML =
:-)</FONT></P>
<P><FONT SIZE=3D2>Concerning the problem I was reporting, it has been =
resolved. Turns out that OmniORB and JacORB were doing everything =
correctly when handling TypeCodes and Anys (which I figured must have =
been the case, otherwise lots of other complaints would have been seen =
by now). The problem was a bug in the JacORB IDL compiler =
generating incorrect TypeCode information under certain =
conditions. I notified the maintainers of JacORB, and it turns =
out they had already found and fixed the problem. For anyone =
interested, they have a fix on the "Known Problems" section =
of their website.</FONT></P>
<P><FONT SIZE=3D2>Thanks again for the help.</FONT>
</P>
<P><FONT SIZE=3D2>Weston Monceaux</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C06060.961B5738--