On 7/13/06, Jimmy, Jing Lv <[EMAIL PROTECTED]> wrote:
Hi:
I'd like to raise the topic on I18N of native code. As discussed
about patch-815, we found there are exceptions thrown by native code
with un-internationalized error message. To resolve this problem, there
may be two solutions:
1) make native code return error code instead of throw exceptions, and
let Java code deal with these errors. This seems pretty good, and also
resolve such problems like 815, but require much more effort to refactor
all native and Java codes. What's more, as some native methods do not
return an integer at all, we may add an output parameter to them, at
least for network-related luni/nio, there are about 10 methods like this.
2) As it is still easy for native code to call Java code, so rewrite
error-message-lookup native method to lookup internationalized message,
e.g., call MsgUtil.getString(). This refactor may be easy, but to
JIRA-815 and other message-dependent Java code, it do no help. So it
still requires other refactoring, e.g., return error code in some
situation like suggested in (1).
Indeed we need to i18d the native code to resolve this issue. I'd suggest to
use the log4cxx & resource bundle approach
for doing this. This one can be suitable for both VMs & API natives. I'm
going to create new thread to discuss this approach.
Thanks,
Vladimir.
Another solution can be: catch exceptions on Java code, replace its
message, and throw out again, this may be too ugly, so I do not suggest
so.
Any suggestions? Thanks!
--
Best Regards!
Jimmy, Jing Lv
China Software Development Lab, IBM
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
