This feature includes resolutions from OMG that affect on-the wire
interoperability for the J2EE Application Servers.  Since CORBA 2.3.1, several
interoperability issues have been submitted and resolved thru OMG.  Since
RMI/IIOP interoperability is one of the main goals of J2EE, Sun's ORB needs to
incorporate resolutions/updates of any interop issues since CORBA 2.3.1.

List of implemented revisions and updates

>From interop RTF ptc/00-11-09:
    Issue 3787: _get_domain_managers ambiguous
	No effect, because the ORB does not implement this method
    Issue 3792: Is padding necessary for empty Reply body?
	Fixed the empty body header alignment problems
    Issue 3576: Absence of Wide Character Code Set
    Issue 3681: CodeSets service context in GIOP 1.0 request
	Implemented in JDK 1.4.
    Issue 4007: wchar alignment in GIOP 1.2

>From interop RTF ptc/ customer -01-18:
 
   Issue 4289: GIOP issue: fragmented replies with exceptions
	The ORB will send an exception response to the request after the 
        error in marshalling the original response.  This may be retried 
        if necessary.
    Issue 4328: Indirection with chunking and fragmentation
	Implemented: will not chunk between the indirection tag
	and indirection offset.
       
>From core RTF 03-01-08:
    
    Issue 4725

>From ptc/ customer -06-07:

    5332: java.rmi.CORBA.Stub serialVersionUID

>From ptc/ customer - customer -01:

    3151: Stream format problem for custom marshalled RMI types
    4319: Behavior of Java writeUTF/readUTF
    4591: Behavior of writeByte, writeChar, writeBytes, writeChar
    4795: RMI-IIOP interop bet. J2SE 1.4 and 1.4
	Implemented in JDK 1.4 
======================================================================

N/A

This feature has been added for Tiger release

======================================================================

Hi,

My name is Luiz Laranjeira. I am a software development manager with SS8 Networks. We use the Sun ORB in our GUI implementation.

A request from a customer has arisen asking us to allow our client GUI to traverse a NAT/VPN.

Has the Sun ORB incorporated the OMG Corba 
Firewall Traversal Specification? In other words, is the new version of the Sun ORB capable of traversing a firewall/NAT?

My e-mail is luiz.laranjeira@ss8.com and I would
really appreciate to hear from you on this.

Regards,

Luiz Laranjeira
Lawful Intercept Software Development Manager
SS8 Networks, Inc
San Jose, CA