Discussion:
[omniORB] Option validateUTF8 seems not to work
Peter Klotz
2012-08-07 10:48:19 UTC
Permalink
Hello

In a simple omniORB 4.1.5 Client/Server setup with option validateUTF8 set to 1 no exception is thrown.

The client (nativeCharCodeSet=UTF-8, validateUTF8=1) sends non UTF-8 byte sequence 0xe4 in an IDL string to the server (nativeCharCodeSet=UTF-8, validateUTF8=1). According to the documentation, I would expect a DATA_CONVERSION exception.

Should this setup trigger the exception?

Regards, Peter.

Peter Klotz
Software Engineer

Phone: +43 (0) 50 86 48-4100
Fax: +43 (0) 50 86 48-4111
E-Mail: <peter.klotz at ith-icoserve.com>
_________________________________________________________

ITH icoserve technology for healthcare GmbH
A-6020 Innsbruck, Innrain 98
www.ith-icoserve.com
Rechtsform: Gesellschaft mit beschr?nkter Haftung
Firmensitz: 6020 Innsbruck, Innrain 98
Firmenbuchnummer: FN 174117f
Firmenbuchgericht: Innsbruck
DVR: 0983039
Duncan Grisby
2012-08-14 12:45:03 UTC
Permalink
Post by Peter Klotz
In a simple omniORB 4.1.5 Client/Server setup with option validateUTF8 set to 1 no exception is thrown.
There is a silly char signedness bug in the validation code. The
attached patch fixes it.

Duncan.
--
-- Duncan Grisby --
-- duncan at grisby.org --
-- http://www.grisby.org --

-------------- next part --------------
A non-text attachment was scrubbed...
Name: utf8.patch
Type: text/x-patch
Size: 583 bytes
Desc: not available
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20120814/57a52f44/attachment.bin>
Loading...