Use the following tutorial http://www.netbeans.org/kb/55/amsecurity.html to
create StockQuoteService from Samples. Deployment of StockQuoteService has an
err message not from pseudo localized bundle file.
I'm running in the Japan locale, using a pseudo localized Netbeans.
The message does not come from the pseudo localized jar file.
Created attachment 42424 [details]
The message "The system cannot find the path specified" does not come from the
j2eeserver, it might come from Ant.
Don't know whether the NetBeansProjects directory should be localized,
reassigning to projects for evaluation.
On what platform? Looks like your operating system does not correctly support
Unicode filenames from Java. Try on Linux (UTF-8 system locale) for comparison,
which should be fine.
This issue is about the message itself "the system cannot find the path
specified" and thats not related to which sublocale, but I see what
you mean that using the multibyte in path name might cause the message in the
and that might be encoding kind of issue.
Will ask that it be tried using a ja utf8 locale and separate issue filed if the
problem is not
seen in en locale - what category should be used ?
it looks ok in Japan. Err message is shown correctly.
In eng locale the IDE couldn't perform this operations (Clean and Build of
StockService) and close:
This is a message on my console:
# An unexpected error has been detected by Java Runtime Environment:
# SIGSEGV (0xb) at pc=0xfafa0f18, pid=8276, tid=25
# Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing)
# Problematic frame:
# C [libX11.so.4+0x20f18] _XFreeExtData+0x10
kaa: the message you get on eng locale means your jvm crashed. That's something that shall not happen and it seems to be
a jvm problem, not netbeans problem.
closing as won't fix, seems to be an operating system problem to me.
please try running "ant jar" on the command line (in the project's root directory). Please reopen if the jvm doesn't
crash on command line but does so persistently within the IDE. Assuming both use the same encoding of course.