Please see the attached test case.

For some CORBA 2.3 features, rmic -iiop recognizes that it will need
2.3 portable streams, so defines local variables which are 2.3 specific.
The main imports are still org.omg.CORBA.portable streams.

In this case rmic -iiop generates code to treat the IDLEntity as an
abstract interface, but doesn't generate local variables to use that
2.3 feature.

It may be incorrect to map the IDLEntity parameter to an abstract
interface.

This prevents use of IDLEntity as a parameter or return type in remote EJB
or RMI-IIOP interfaces.