[omniORB] omniORBpy, Python 2.0 and unicode

[uche.ogbuji@fourthought.com]

Based on quick and dirty tests, if you pass a Python unicode object in a 
string-type argument using omniORBpy and omniORB (latest CVS), you get a CORBA 
BAD_PARAM exception.

The Python/CORBA binding doesn't say anything about unicode.  Understandable 
since it predates Python/Unicode, but it seems to make sense that Python 
unicode strings should be accepted as string data.  For one thing, this would 
parallel the Java binding.

Am I right that one can't use unicode objects for string parameters in 
omniORBpy?  Are there any plans to change this?  Using omniORB for XML 
processing (in 4Suite Server), one runs into many unicode objects and it would 
be quite a burden to precede every CORBA invocation with code for character 
encoding.

Thanks.


-- 
Uche Ogbuji                               Principal Consultant
uche.ogbuji@fourthought.com               +1 303 583 9900 x 101
Fourthought, Inc.                         http://Fourthought.com 
4735 East Walnut St, Ste. C, Boulder, CO 80301-2537, USA
Software-engineering, knowledge-management, XML, CORBA, Linux, Python