This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 25663 - I18N Exception massage looks grabage
Summary: I18N Exception massage looks grabage
Status: CLOSED INVALID
Alias: None
Product: obsolete
Classification: Unclassified
Component: jndi (show other bugs)
Version: -FFJ-
Hardware: Sun Solaris
: P3 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2002-07-16 10:15 UTC by jf4jbug
Modified: 2003-07-31 12:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Snap-shot on Solaris (3.58 KB, image/gif)
2002-07-16 10:20 UTC, jf4jbug
Details
Snap-shot on linux (22.01 KB, image/jpeg)
2002-07-16 10:22 UTC, jf4jbug
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jf4jbug 2002-07-16 10:15:56 UTC
Using Orion ML Build 020624 on Solaris or linux,
the problem of the following 
character garbage occurs.

To reproduce:

    1) Open [Runtime] tab in [Enplorer]
    2) Open [JNDI] and [Providers]
¡¡¡¡3) Right-click any factory such as
'RegistryContectFactory' 
       and select [Connect Using ...]

       At this point, "New JIDI Context" dialog
appears.     
       
¡¡¡¡4) Enter any characters such as 'test' to
[Context Label]
¡¡¡¡5) Click [OK] button

	At this point, "Exception" dialog appears, but
the messages look garbage.
	
 	    java.rmi.ConnectException: Connection
refused to host: localhost; nested exception is:
 	   	java.net.ConnectException: Connection
refused
					   --- grabage ------

The message is displayed in English on Windows, so
this problem do not occurs.
Comment 1 jf4jbug 2002-07-16 10:20:53 UTC
Created attachment 6689 [details]
Snap-shot on Solaris
Comment 2 jf4jbug 2002-07-16 10:22:01 UTC
Created attachment 6690 [details]
Snap-shot on linux
Comment 3 Marek Grummich 2002-07-22 10:59:32 UTC
Set target milestone to TBD
Comment 4 Tomas Zezula 2002-10-16 10:20:17 UTC
The problem is in the nested exception. The dialog displays the
catched exception (thrown by JNDI) and this exception contains nested
one (possibly thrown by the remote service). The problem is that the
JNDI exception is not localized and the remote exception is probably
localized.
This problem can not be solved in the JNDI module, the only one
solution in the JNDI module is not to display the exception to the
user and display just information like "Can not set up connection to
service", but this is not good way to go.

Could you send me the version of JDK and provider used, I will report
it as an issue to JDK.
Comment 5 Jesse Glick 2002-12-23 16:55:56 UTC
Consistent use of the I18N keyword.
Comment 6 Tomas Zezula 2003-03-04 10:01:18 UTC
See comment above.
Comment 7 yasuhiro 2003-07-31 12:00:22 UTC
This issue does not occur on the following environment.

OS: Win2K, RedHat 7.2ja, Sol8 (ja locale)
J2SDK: 1.4.0_02 or 1.4.2
IDE: NetBeans 3.5.1 ML-JA (build 030725) or Sun ONE Studio 5