[omniORB] Unicode codesets

[Brett Zimmerman]

Hi All,
	I am trying to use omniORB4 in a Unicode solution with the Servant
running on Solaris and the client running on Windows. From what I
understand, if I were to use the inbuilt UCS-4 encoding for the
nativeWCharCodeSet on the Solaris side, and leave the Windows client
codesets as UTF-16, then the UCS-4 codeset implementation would convert the
strings to UTF-16. 
>From the manual - 9.3 Implementing new code sets:
'If the transmission code set does not know how to handle the native code
set, it converts the string/wstring into UTF-16, and passes that to the
native code set object (or vice-versa). All code set implementations must
therefore know how to convert to and from UTF-16.'
Am I interpreting this correctly? 

A call to proxyPushConsumer->obtain_subscription_types() from the windows
client in generating the following trace:
omniORB: throw UNKNOWN from GIOP_C.cc:241 (NO,UNKNOWN_UserException)
with the following exception being thrown further along:
omniORB: throw MARSHAL from cs-8bit.cc:361
(YES,MARSHAL_StringNotEndWithNull)

The servant trace contains nearly 50000 of the following exceptions:
omniORB: WARNING -- method 'add_constraints' raised an unexpected exception
(not a CORBA exception).
followed by the following exception
omniORB: throw giopStream::CommFailure from
giopStream.cc:1103(0,NO,COMM_FAILURE_UnMarshalArguments)

Has anyone successfully implemented a UCS-4 to UTF-16 Unicode Solution?
Any advice would be greatly appreciated.
TIA,
	Brett Zimmerman